fix: Edits to replication specs for cluster

[EspenAlbert]

Proposed changes

1. Adds e2e test for cluster
2. Fix: Edits to replication specs for cluster

Test Summary

1. Create a GEOSHARDED cluster with a single replication spec (zone1) with 3 nodes
2. Update the cluster:
   • Change from 3->5 nodes in zone1
   • Add a new replication spec (zone2) with 5 nodes
3. Assert the replication_id is kept on the 1st replication spec, and a new replication spec is added and both replication specs have 5 nodes

Fix Summary

The fix reads the current cluster if replication specs are set and "matches" replication IDs. See the unit tests in mappings_test for the matching details.

Note: We couldn't reuse the Terraform implementation since CFN doesn't store the full state of the resource. It only receives the template used for the update call; this means the replication_spec IDs will never be set on the prevModel or currentModel (this behavior was "discovered" by trying an initial fix of updating the replication specs of the currentModel during create)

Bug reproduced & fix screenshots

Example of failing e2e test (Github action before fix committed)

Screenshot from CFN:

Example of passing e2e test (Github action after fix committed)

Screenshot from CFN:

Link to any related issue(s): CLOUDP-256730 and CLOUDP-256534

Type of change:

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update
• [ ] 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.

Manual QA performed:

• [x] cfn invoke for each of CRUDL/cfn test
• [ ] Updated resource in example
• [ ] Published to AWS private registry
• [ ] Used the template in example to create and update a stack in AWS
• [ ] Deleted stack to ensure resources are deleted
• [ ] Created multiple resources in same stack
• [ ] Validated in Atlas UI
• [ ] Included screenshots

Required Checklist:

• [x] I have signed the MongoDB CLA
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
• [x] I have added any necessary documentation (if appropriate)
• [x] I have run make fmt and formatted my code
• [x] For CFN Resources: I have released by changes in the private registry and proved by change works in Atlas

Further comments

contract tests: