feat(gapic-generator): Add NullMarked annotation to generated classes

[nnicolee]

This PR updates the gapic-generator-java to add the JSpecify @NullMarked annotation to all generated class declarations. Adding @NullMarked at the class level defines the class scope as null-safe, establishing that all unannotated types in method signatures (parameters and return types) are nonnull able by default. This is the first phase in onboarding the generated client libraries to compile-time safety validation, see design doc for more details: go/sdk:java-jspecify-null-annotations-gapic

Classes Annotated:

• Client Classes: AbstractServiceClientClassComposer
• Settings Classes: AbstractServiceSettingsClassComposer and AbstractServiceStubSettingsClassComposer
• Stub Classes: AbstractServiceStubClassComposer and AbstractTransportServiceStubClassComposer
• Callable Factories: AbstractServiceCallableFactoryClassComposer
• Resource Names: ResourceNameHelperClassComposer, CommonStrings

Implementation Changes:

• Added JSpecify import statements to class-level generation templates
• Registered NullMarked.class and Nullable.class in TypeStore across all class composers to ensure references compile and resolve properly
• Updated goldens (generator + java-showcase) + dependencies for the build

Verification/Testing:

• Please refer to this doc: https://docs.google.com/document/d/1h126pbTGqSwtJyl35E2_vQjM9gNtmWETYCM7PObcvmQ/edit?tab=t.0#heading=h.s4q06jxocx8b

Revisions:

• Added JSpecify to all proto pom.xmls

Next Steps:

• In the next PR, will add @nullable annotations

[gemini-code-assist]

Code Review

This pull request adds the org.jspecify:jspecify dependency to multiple pom.xml files across various Google Cloud Java proto modules. However, in the java-bigtable modules, the dependency was incorrectly placed inside the <dependencyManagement> block instead of the <dependencies> block. Additionally, since these pom.xml files are auto-generated, manual edits should be avoided to prevent them from being overwritten; instead, the generator or source metadata should be updated.

[gemini-code-assist]

Avoid manually editing auto-generated files like pom.xml in generated client libraries because changes will be overwritten. To ensure the jspecify dependency is correctly placed in the <dependencies> block instead of <dependencyManagement>, please modify the generator or the source metadata instead.

References

1. Avoid manually editing auto-generated files (such as pom.xml in generated client libraries) because changes will be overwritten. Modify the generator or the source metadata instead.

[gemini-code-assist]

Avoid manually editing auto-generated files like pom.xml in generated client libraries because changes will be overwritten. To ensure the jspecify dependency is correctly placed in the <dependencies> block instead of <dependencyManagement>, please modify the generator or the source metadata instead.

References

1. Avoid manually editing auto-generated files (such as pom.xml in generated client libraries) because changes will be overwritten. Modify the generator or the source metadata instead.

[sonarqubecloud]

Quality Gate failed for 'gapic-generator-java-root'

Failed conditions
6.2% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed for 'gapic-generator-java-root'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud