chore: Remove usage of fixed 2024-08-05 version in cluster resource and ensure auto scaling mode is not impacted

[AgustinBettati]

Description

Link to any related issue(s): CLOUDP-291400

When cluster resource requires using latest API is was fixed to 2024-08-05 version out of caution before doing ISS autoscaling epic. With proper testing now in place, we can safely use latest version instead of 2024-08-05 for specific PATCH requests that are made.

Type of change:

• Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
• New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
• Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contributing guides
• I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code
• If changes include deprecations or removals I have added appropriate changelog entries.
• If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.

Further comments

[AgustinBettati]

ensure that even if redact_client_log_data is enabled (calling PATCH 2024-10-23) autoscaling mode is not impacted (because request does not include replicationSpecs/autoScaling properties)

[AgustinBettati]

failing test is unrelated to changes, syncing with Aastha for fixing that test

[EspenAlbert]

LGTM

[github-actions]

This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!