[valerena]

All tests work fine with whatever minor version of ruby exists, so there's no need to specify 3.4.7, since 3.4 should work just fine. This prevents us having to update the version to the latest one every once in a while.

For the sync test, the "before" ruby version was set as 3.2, but the Lambda function was actually configured as 3.4 already, so I also updated that to 3.4, since the "before/after" change is not related to the version.

Which issue(s) does this change fix?

Why is this change necessary?

• A recent update in GitHub Runners broke all tests because we had an old version of Ruby pinned.

How does it address the issue?

• Stop pinning the patch version (like 3.2.7) and just keep major.minor a.k.a. 3.2, 3.3 and 3.4

What side effects does this change have?

We don't know exactly the Ruby version being used, since it will just whatever chooses by default.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Review the generative AI contribution guidelines
• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[valerena]

Integ tests: https://github.com/aws/aws-sam-cli/actions/runs/42311009784/job/128252083694
There's one unrelated test failure in a MicroVM test.