Configure Java toolchains per project

[UNIDY2002]

Summary:

A follow-up fix on #40560

The fix introduced by #40757 worked under the false assumption that :app gets evaluated before any other library. However, some libraries, such as @amplitude/analytics-react-native (whose project name is :amplitude_analytics-react-native), might be evaluated before :app and miss the configureJavaToolChains() process.

This PR changes configureJavaToolChains() into a per-project implementation, and invokes the function during both library and app configurations. This can ensure that all projects get their Java toolchains configured promptly.

Changelog:

[ANDROID] [FIXED] - Configure Java toolchains per project

Test Plan:

Test with @amplitude/analytics-react-native and ensure that the android app builds in new arch.

• Before: https://github.com/UNIDY2002/repro-rn-73-java-new-arch/actions/runs/6745744156/job/18338149263
• After: https://github.com/UNIDY2002/repro-rn-73-java-new-arch/actions/runs/6745838309/job/18338439143

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	17,657,093	-2
android	hermes	armeabi-v7a	n/a	--
android	hermes	x86	n/a	--
android	hermes	x86_64	n/a	--
android	jsc	arm64-v8a	21,034,736	-4
android	jsc	armeabi-v7a	n/a	--
android	jsc	x86	n/a	--
android	jsc	x86_64	n/a	--

Base commit: 80d816a
Branch: main

[UNIDY2002]

Wait... This fix is having issue on old arch...

[UNIDY2002]

Libraries on old arch does not apply the RNGP, and will not get their Java toolchains configured. Therefore, this PR is inapplicable.

Closing it for now.

[cortinico]

However, some libraries, such as @amplitude/analytics-react-native (whose project name is :amplitude_analytics-react-native), might be evaluated before :app and miss the configureJavaToolChains() process.

Projects are not evaluated alphabetically (order is arbitrary). So you should not need this fix at all in the first place

EDIT: You were right. This is a bug (see #41620). Fix is forthcoming