chore: sdk-platform-java partial release preparation

[suztomo]

The modules in sdk-platform-java should be non-SNAPSHOT.
Other modules are still in their SNAPSHOT versions but their build
should succeed.

b/500385320

[suztomo]

Until the references to the sdk-platform-java modules exists, the build would fail. This still needs #12690.

[gemini-code-assist]

Code Review

This pull request prepares a release by updating version strings across numerous pom.xml files and the versions.txt file, moving from -SNAPSHOT to release versions. Feedback highlights significant version inconsistencies where several modules, including google-common-protos and various google-iam components, are being set to .0 versions instead of the expected .1 release versions. These discrepancies appear to stem from missed updates in the versions.txt file and should be corrected to ensure a consistent release state.

[gemini-code-assist]

The version for google-common-protos-parent is being updated to 2.67.0, which is the current released version, effectively reverting it from 2.67.1-SNAPSHOT. In contrast, other modules in this PR (e.g., api-common, gax, google-cloud-core) are correctly moving from .1-SNAPSHOT to .1. This inconsistency suggests that versions.txt was not updated for proto-google-common-protos. If this module is intended to be part of the release, it should be set to 2.67.1.

Suggested change

	<version>2.67.0</version><!-- {x-version-update:proto-google-common-protos:current} -->
	<version>2.67.1</version><!-- {x-version-update:proto-google-common-protos:current} -->

[gemini-code-assist]

The version for google-iam-parent is being set to 1.62.0, which is inconsistent with the rest of the release preparation. Notably, google-iam-policy is correctly updated to 1.62.1 in versions.txt (line 590), and other core modules are moving to .1. Reverting the parent to 1.62.0 while related modules move to 1.62.1 will cause version mismatches. This should likely be 1.62.1.

Suggested change

	<version>1.62.0</version><!-- {x-version-update:proto-google-iam-v1:current} -->
	<version>1.62.1</version><!-- {x-version-update:proto-google-iam-v1:current} -->

[gemini-code-assist]

Multiple dependencies in this BOM (including common-protos and various iam modules) are being set to versions ending in .0 (e.g., 2.67.0, 1.62.0), while other modules in the same PR are moving to .1. This is particularly problematic for the IAM modules since google-iam-policy is being released as 1.62.1. These should likely all be updated to their .1 counterparts to ensure a consistent release state.

[gemini-code-assist]

While gax-grpc and other modules are correctly updated to .1 for release, several subsequent entries in this file (e.g., proto-google-common-protos at line 984 and proto-google-iam-v1 at line 986) appear to have been missed. This is causing the POM files to be updated to the old .0 versions instead of the intended .1 release versions. Please ensure all modules targeted for this partial release are updated in this file.

[suztomo]

Error: 4:389 [ERROR] Failed to execute goal on project google-auth-library-appengine: Could not resolve dependencies for project com.google.auth:google-auth-library-appengine:jar:1.43.1-SNAPSHOT
Error: 4:389 [ERROR] dependency: com.google.api:api-common:jar:2.59.1 (compile)
Error: 4:389 [ERROR] 	Could not find artifact com.google.api:api-common:jar:2.59.1 in google-maven-central-copy (https://maven-central.storage-download.googleapis.com/maven2)
Error: 4:389 [ERROR] 	Could not find artifact com.google.api:api-common:jar:2.59.1 in maven-central (https://repo1.maven.org/maven2)
Error: 4:389 [ERROR] 	com.google.api:api-common:jar:2.59.1 was not found in https://maven-central.storage-download.googleapis.com/maven2/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of google-maven-central has elapsed or updates are forced
Error: 4:389 [ERROR] -> [Help 1]