Remove transitive modifier from optional dependencies

[ppkarwasz]

This PR:

• Add a Groovy script that checks the generated module-info.class files for static transitive dependencies.
• Modifies the BND configuration not to mark org.jspecify as transitive.

We remove the transitive modifier from all optional dependencies.

Closes #2929.

Note: Once these changes are accepted, I'll move the Groovy script to logging-parent and implement apache/logging-parent#196 too.

[vy]

Question: Shouldn't we instead

• enforce a whitelist of static dependencies (so every optional will need to be a conscious decision, not a mistake) and
• ban transitive static?

[ppkarwasz]

Question: Shouldn't we instead

* enforce a whitelist of `static` dependencies (so every optional will need to be a conscious decision, not a mistake) and

I am not sure whether to whitelist our optional dependencies or all our runtime dependencies. In general there is a mismatch between the scope of Maven dependencies and the OSGi and JPMS optionality.

In general the agreement is that BND should not automatically mark as optional the packages in optional Maven dependencies (see bndtools/bnd#2713), but I believe it could at least warn about required packages, which are optional Maven dependencies.