APIBot: SDK update based on recent changes in Atlas API

[svc-apix-Bot]

Automatic update for MongoDB Atlas Go Client based on OpenAPI changes.
PR contains autogenerated changes for the MongoDB Atlas client.

Automated checks

1. Compilation and unit tests
2. Documentation style
3. Transformation engine linting

Important Details

1. If the build is failing please check the logs and fix the issues in the OpenAPI file (openapi/atlas-api.yaml)
2. Do not attempt to manually fix any issues in the Golang code as all changes are automatically generated.
   Fixes should be applied to the OpenAPI file (openapi/atlas-api.yaml) or ./tools engine in a separate PR.

Manual Review Procedure

1. Review changes in the OpenAPI file (openapi/atlas-api.yaml)
2. If PR contains breaking changes, review ./releaser/breaking_changes/{release_version}.md file
3. Approve and merge PR into the main branch
4. After the merge automated release process will be triggered.

Troubleshooting

To skip release process after merge please revert changes from version.go file.
Release can be triggered by restoring changes in version.go.

[augmentcode]

🤖 Augment PR Summary

Summary: This PR updates the generated Atlas Go SDK to align with recent Atlas Admin API (OpenAPI) changes.

Changes:

• Clarifies Streams networking docs for GCP, noting that PRIVATE_LINK corresponds to Private Service Connect (PSC) and how connectionId is interpreted
• Adds the new alerting/search metric SEARCH_PROCESS_THROTTLING and a corresponding raw metric threshold schema to the OpenAPI spec
• Bumps the SDK version constant to v20250312018.2.0
• Updates OpenAPI generator metadata (x-xgen-sha)

Technical Notes: The OpenAPI changes include new discriminator/mapping entries and a new schema for threshold configuration; ensure downstream transforms/codegen consume these updates as intended.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

SearchProcessThrottlingRawMetricThresholdView (and the new SEARCH_PROCESS_THROTTLING discriminator entries) are added to openapi/atlas-api.yaml, but they don’t appear in openapi/atlas-api-transformed.yaml in this PR; if the SDK is generated from the transformed spec, this new metric may be dropped. Consider confirming the transform/codegen pipeline is updated so this metric is actually exposed/handled by generated clients.

Severity: medium

Other Locations

• openapi/atlas-api.yaml:21424
• openapi/atlas-api.yaml:21800
• openapi/atlas-api.yaml:22095
• openapi/atlas-api.yaml:22254

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}