jpms: add 'require static' entries for annotation processing

[jjohannes]

Follow up to: #2970

The annotation libraries that provide annotations used on public API should be declared as require static. Otherwise, compiling with -Xlint:all and -Werror fails because all annotations that are visited need to be accessible from the context of the module they are used in.

Example error:

guava-33.4.5-jre.jar(/com/google/common/util/concurrent/ListenableFuture.class): warning: Cannot find annotation method 'value()' in type 'DoNotMock': class file for com.google.errorprone.annotations.DoNotMock not found
guava-33.4.5-jre.jar(/com/google/common/util/concurrent/ListenableFuture.class): warning: Cannot find annotation method 'value()' in type 'DoNotMock': class file for com.google.errorprone.annotations.DoNotMock not found
error: warnings found and -Werror specified
1 error
2 warnings

https://scans.gradle.com/s/ose6lkdbtogww/console-log/task/:hedera-protobuf-java-api:compileJava?anchor=5&page=1

For more details see also this similar issue in Log4j2: apache/logging-log4j2#3437

I believe Guava's own build would fail without this at compilation time if annotation processing would be done on the module path (--process-module-path).
Unfortunately, that's a bit complex to configure currently: https://issues.apache.org/jira/browse/MCOMPILER-412

[cpovirk]

Hi, again, and thanks.

I agree that the lack of a requires line is wrong. I am going to try to spend a little more time to actually understand modules (based in part on a dev.java tutorial, which seems very helpful to my untrained eye) enough to decide whether to first try something other than requires static. But I don't want to drag that on too long, given that requires static should be strictly better than what we have now.

I left some notes in jspecify/jspecify#495 (comment).