We should expand our Bazel documentation to include:

• - Installing the Bazel plugin in Android Studio Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723
• - Importing the project as a Bazel project Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723
• - Syncing (& partial syncing)
• - Building the app Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723
• - Building & running tests through AS Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723

Also, per #3371 Bazel development support is very limited on Windows. Per #3437 we should investigate the viability of setting up a VM and running both Android Studio and Bazel from the same Unix-based environment (to avoid a bifurcation where the repo lives in Windows and the user does development via Windows Android Studio, but uses Bazel within an Ubuntu subsystem). This involves documenting the steps below for Windows:

• - Using git to clone & modify Oppia Android
• - Running Android Studio
• - Building & running tests via Bazel (CLI) Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723
• - Deploying the app binary & tests to a real device Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723
• - Starting an emulator Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723
• - Deploying the app binary & tests to an emulator Fix #2746 and Fix part of #1723: Update Onboarding Instructions and Bazel Documentation #5723