java_import should support add_opens and add_exports

[timothyg-stripe]

Description of the feature request:

2217b13 adds support for add_opens and add_exports attributes to java_library, java_binary, and java_import. But java_import is left out.

java_import should support these attributes too.

Which category does this issue belong to?

Java Rules

What underlying problem are you trying to solve with this feature?

We currently use java_import to import the release jars for google-java-format, which require the following flags in order to run without warnings:

--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.code=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED
--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED

We could work around this issue by adding a java_library wrapper, but this is inconvenient.

Which operating system are you running Bazel on?

macOS

What is the output of bazel info release?

release 6.2.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse master; git rev-parse HEAD ?

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[timothyg-stripe]

cc @cushon

who wrote 2217b13

[timothyg-stripe]

@iancha1992 Can we backport #20035 to 7.0?