Create a BUILD.bazel file for domain/onboarding

[fsharpasharp]

This task is part of the build system migration from Gradle to Bazel.

Prerequesites

• Make sure you are able to build Oppia using Bazel
• Follow the Oppia Bazel Setup instructions to setup Bazel and learn the terminology.
• Read the Gradle Bazel Migration Best Practies and FAQ for more context and see if there's an answer there to any question you have.

Task

1. Create a BUILD.bazel file in

domain/src/main/java/org/oppia/android/domain/onboarding/

and

domain/src/main/java/org/oppia/android/domain/onboarding/testing

2. Define the kt_android_library library/libraries

Based on the imports in the Kotlin files, add the required third_party dependencies to make the libraries build. Check the Useful links section for a list of third_party dependencies. You may also need to add the non third_party dependencies.

Create libraries to separate interfaces, annotations and implementations. Often we can split a package into the libraries: api, module and interface.

3. Add the directory to the MIGRATED_PROD_FILES of the module's root BUILD.bazel file

4. Add the libraries to the list of deps dependencies in the targets that require the library

You will have to set the apropriate visbility. See the list of visibilities in the link below.

5. Clean up any unused deps dependencies

6. Verify that the app builds

Useful links

• BUILD.bazel files
• Visibilities
• third_party dependencies

[rishidyno]

@JonathanAlvares if you are not working on this issue, @fsharpasharp can you assign me this issue.

[rt4914]

@rishidyno Un-assigning you from this issue because of inactivity, please re-assign yourself if you are currently working on this.