The check & related scripts required fairly involved reworking since the
Maven install file (from which it sources Maven URL context) changed in
format as part of the upgrade for rules_jvm_external. This has actually
led to what seems to be more correct analysis of libraries that the
build depends on, so more licenses have been added to the
maven_dependencies.textproto tracking file.

One unused Crashlytics dependency was removed since it was referencing
an old license that doesn't exist anymore (and the artifact should be
replaced in full by more recent Firebase Crashlytics dependencies that
we are already using).

This addresses an underlying bug with the command executor that can, in
some cases, break compute_affected_tests. It also refines some of its
internal mechanisms for much better performance on expensive PRs.

It also prepares the base support needed for merge queues, but the
CI workflows aren't being updated in this change.

This prepares for merge queues (but doesn't quite configure the workflow
for them--that will happen in a different PR), and improves how tests
are computed for stacked PRs.

…xternal

Conflicts:
	scripts/src/java/org/oppia/android/scripts/common/BUILD.bazel
	scripts/src/java/org/oppia/android/scripts/license/MavenDependenciesListCheck.kt
	scripts/src/java/org/oppia/android/scripts/license/MavenDependenciesRetriever.kt
	scripts/src/java/org/oppia/android/scripts/maven/GenerateMavenDependenciesList.kt
	scripts/src/javatests/org/oppia/android/scripts/license/MavenDependenciesListCheckTest.kt
	scripts/src/javatests/org/oppia/android/scripts/license/MavenDependenciesRetrieverTest.kt
	scripts/src/javatests/org/oppia/android/scripts/maven/GenerateMavenDependenciesListTest.kt

Also, update TODO check script to have nicer output, and support
generating the exemption textproto file for easier updates in the
future.

…xternal

This moves the codebase to using the recommended single top-level Dagger
library rather than replicating it in a bunch of different places.

This is needed for downstream work. It also includes ensuring that Guava
JRE can never be used (since only Android should ever be referenced by
the production app build).

…xternal

The new proto target isn't used anywhere so this was missed.

…xternal

Conflicts:
	scripts/assets/todo_open_exemptions.textproto

…xternal

Conflicts:
	scripts/assets/test_file_exemptions.textproto
	third_party/maven_install.json

Conflicts:
	app/src/main/java/org/oppia/android/app/translation/BUILD.bazel
	third_party/maven_install.json

These issues were found after I started using a new development
environment.

ProfileAndDeviceIdFragmentTest had been updated to use a newer fragment
initialization pattern, but that's no longer needed and seems to be
causing what appears to be timing discrepancies between local dev and
CI.

The issue ultimately arose from test parameters being initialized after
they're needed in the launched UI. This type of change was tried earlier
in the branch, but reverted since it didn't seem necessary. It is,
however, necessary when there are environment differences (e.g. local
vs. CI) or when running certain tests individually.

Due to the difficulty in finding this issue, ActivityScenarioRule has
been added as a prohibited pattern in the static regex checks (along
with ActivityTestRule since that's deprecated and discouraged, anyway).

The test was suffering from some proto encoding inconsistencies that
seem to occur between some development machines vs. on CI. The fix
improves the test's robustness by extracting the raw encoded string,
verifying that the other outputs in the intent message correctly
correspond to that string, and that the string (as a parsed proto)
contains the correct values. As a result, the test no longer depends on
a hardcoded encoding value to be present for verification. This does
result in a bit more logic than is generally good to have in a test (and
it lengthened the test code quite a bit), but it seems necessary in this
particular case.

…cted-tests

Conflicts:
	scripts/assets/todo_open_exemptions.textproto
	scripts/src/javatests/org/oppia/android/scripts/ci/ComputeAffectedTestsTest.kt
	scripts/src/javatests/org/oppia/android/scripts/common/GitClientTest.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoIssueResolvedCheckTest.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoOpenCheckTest.kt

…cted-tests

Conflicts:
	scripts/assets/todo_open_exemptions.textproto
	scripts/src/javatests/org/oppia/android/scripts/ci/ComputeAffectedTestsTest.kt
	scripts/src/javatests/org/oppia/android/scripts/common/GitClientTest.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoIssueResolvedCheckTest.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoOpenCheckTest.kt

This doesn't address all timeouts being observed in scripts. More
analysis may be needed.

This does a bunch of other small things, too, but the main difference
here is introducing support for interacting with GitHub via its REST API
rather than requiring the user to use the 'gh' tool locally (though the
gh CLI tool is still needed for maintaining authentication access).

Tests still need to be added, and some cleanup is needed once the
branch's base is adjusted.

This is a script-specific dispatcher which will allow for better
asynchronous support in upcoming PRs (especially for command execution).
This change serves to prepare for those changes.

The main change here is ensuring that Bazel 4.0.0 is used & bzlmod
disabled in newer versions of Bazel when running operations in a test
Bazel environment.

This commit also introduces some more timing tweaks on CommandExecutor
for some tests, though these only affect very specific tests (as many
script tests directly call a script's main() function and thus don't
overwrite its executor behavior).

This commit attempted to introduce "--batch" mode to runs, but the
isolation didn't actually seem to improve stability and, instead,
substantially slowed down some of the tests.

…ipt-execution-support

Conflicts:
	scripts/src/java/org/oppia/android/scripts/ci/ComputeAffectedTests.kt
	scripts/src/javatests/org/oppia/android/scripts/ci/ComputeAffectedTestsTest.kt
	scripts/src/javatests/org/oppia/android/scripts/common/BazelClientTest.kt

Plus, actually makes use of the new script background dispatcher in
CommandExecutorImpl to make the new wiring make more sense (though its
real utility will come in a follow-up PR).

…do-check-locally-runnable

This makes the TODO open check script runnable using the script
background dispatcher, and fixes some tests so that they pass now.

More documentation and testing work is still needed to finalize this PR.

…ipt-execution-support

…do-check-locally-runnable

…affected-tests

Conflicts:
	scripts/assets/todo_open_exemptions.textproto
	scripts/src/java/org/oppia/android/scripts/ci/ComputeAffectedTests.kt
	scripts/src/java/org/oppia/android/scripts/common/BazelClient.kt
	scripts/src/java/org/oppia/android/scripts/common/CommandExecutorImpl.kt
	scripts/src/java/org/oppia/android/scripts/common/GitClient.kt
	scripts/src/java/org/oppia/android/scripts/todo/BUILD.bazel
	scripts/src/java/org/oppia/android/scripts/todo/TodoOpenCheck.kt
	scripts/src/javatests/org/oppia/android/scripts/ci/ComputeAffectedTestsTest.kt
	scripts/src/javatests/org/oppia/android/scripts/common/ScriptBackgroundCoroutineDispatcherTest.kt
	scripts/src/javatests/org/oppia/android/scripts/testing/TestGitRepositoryTest.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoIssueResolvedCheckTest.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoOpenCheckTest.kt

…ia-android into upgrade-compute-affected-tests

Conflicts:
	scripts/assets/todo_open_exemptions.textproto
	scripts/src/java/org/oppia/android/scripts/testing/TestBazelWorkspace.kt
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoOpenCheckTest.kt

…xternal

Conflicts:
	scripts/assets/test_file_exemptions.textproto
	scripts/src/javatests/org/oppia/android/scripts/maven/RetrieveLicenseTextsTest.kt

This was done by removing the //testing dependency and, instead, having
instrumentation targets depend on the direct module within //testing
that they need to build. This module & its corresponding implementation
binding (and tests) needed to be moved out of //testing and into their
own /firebase package.

…ecific-issues

Also includes some minor clean-ups within TestBazelWorkspaceTest.

…ecific-issues

…ipt-execution-support

…do-check-locally-runnable

…ipt-execution-support

…do-check-locally-runnable

…ecific-issues

…ecific-issues

…ipt-execution-support

…do-check-locally-runnable

…affected-tests

Required upgrade of kotlinx-coroutines-core.

…do-check-locally-runnable

…ntTest.kt

Co-authored-by: Adhiambo Peres <59600948+adhiamboperes@users.noreply.github.com>

…ipt-execution-support

Conflicts:
	third_party/maven_install.json

…do-check-locally-runnable

Add new FakeCommandExecutor utility + tests.

Add missing GitHub workflow update.

…ipt-execution-support

…do-check-locally-runnable

…affected-tests

Conflicts:
	scripts/assets/todo_open_exemptions.textproto
	scripts/src/javatests/org/oppia/android/scripts/todo/TodoOpenCheckTest.kt

…xternal

Conflicts:
	scripts/assets/maven_dependencies.textproto
	third_party/maven_install.json

Updates the utilities for the Maven dep list & updater scripts to have
much more robustness when trying to verify the correct repository URLs
for artifact coordinates, and when downloading artifact POM files. The
main robustness changes come in the form of retries and smarter
parallelization and error checking.

These changes were necessary due to one of my workstations frequently
flaking out on large numbers of URL blocks during verification, and this
helps considerably.

…do-check-locally-runnable