Add loads for certain py/java rules

[ted-xie]

Bazel 8 removes native shell, python, and java rules. This PR makes rules_robolectric compatible with Bazel 8.

[ted-xie]

Provided this PR gets merged, we (the Bazel team) would also need a release cut relatively quickly in order to unblock the next rules_android release, which will unblock the upcoming Bazel 8 release.

[ted-xie]

@Bencodes @Wyverald There ended up being some kind of java toolchain issue when I tried upgrading rules_java to 8.5.1 for the example app:

ERROR: /home/runner/.cache/bazel/_bazel_runner/faa3a579053c5258adca3d7c148553b6/external/rules_java_builtin/toolchains/BUILD:254:14: While resolving toolchains for target @@rules_java_builtin//toolchains:platformclasspath (b8277ad): No matching toolchains found for types @@bazel_tools//tools/jdk:bootstrap_runtime_toolchain_type.

Note that this only occured with WORKSPACE mode. I tried debugging this for a while but wasn't able to come up with anything concrete. I suspect it's something to do with the native Android rules in rules_android v0.1.1 interacting badly with the latest rules_java, but upgrading the Android rule dep in WORKSPACE was unsavory to say the least.

The only reason I wanted to upgrade rules_java in the first place was to get the rules_java version of http_jar(), but that involved pulling in a lot of complicated WORKSPACE setup and the aforementioned toolchain issue. The next best solution I could think of was to copy over the (fairly standalone) http_jar() rule into robolectric itself, which is also gross, but much less complicated than making WORKSPACE builds work.

[utzcoz]

@ted-xie Just require extra modifications for Buildfier.

[utzcoz]

@Bencodes Maybe you can release a new version based #95 and 4.14.1 release.

[utzcoz]

LGTM.

[utzcoz]

@Bencodes @ted-xie New bazel patch release here: https://github.com/robolectric/robolectric-bazel/releases/tag/4.11.1.1 and bazelbuild/bazel-central-registry#3309.

[Bencodes]

@ted-xie and I chatted about this one further and think that this is probably the least-hacky solution for the underlying issue.

We talked about some alternatives here like letting the workspace and module file diverge, and even patching rules_android. But both of these kind of have downsides that might cause more issues for our end users than just copying http_jar over in the short term.

[Bencodes]

#122