ci: update integration and coverage workflow python version

[brahmanim]

Resolves

ACA-6690

SUMMARY

Updates Python version to 3.13 in integration and coverage test workflows.

Changes:

• Set PYTHON_VERSION to 3.13 in coverage_test.yml
• Set PYTHON_VERSION to 3.13 in integration.yml
• Install community.general tests dependancy.
• The AMI lookup for Fedora-Cloud-Base-39-* returned no images — those Fedora 39 AMIs are no longer available in AWS. Updated AMI filters Owner: 125523088429 (CentOS Community Platform Engineering)
  Name: Fedora-Cloud-Base-.x86_64-4 (matches current Fedora 4x images, excludes ELN/Rawhide)
• Update coverage_test to run only on push, instead of each pull_request.
• Fix integration test test_backup_select_resources - update iam create role to include ansible-test prefix.
• Fix integration test test_deploy_flask_app - Gather information about RDS engine version instead of using a constant var value.
• Fix integration test test_deploy_flask_app - update bastion_host_iam_role iam create role to include ansible-test prefix.
• Fix integration test test_move_objects_between_buckets - The failure comes from stricter validation in amazon.aws.s3_object: object keys must not start with /, the integration test was putting an object at /template/test.txt, but the rest of the test already expects template/test.txt (no leading slash)
• Fix integration test test_customized_ami - use setup_rsa_keys__path with ansible.builtin.file instead of tempfile.
• Update roles/deploy_flask_app - Move key path from /tmp/id_rsa → ~/.ssh/workers_id_rsa
• Fix integration test test_deploy_flask_app - Fixing bastion user_data in test_deploy_flask_app to use dnf and Fedora-appropriate packages.
• Update roles test_customized_ami and test_customized_ami - to install coverage on the bastion host for coverage collection.
• Updated test_customized_ami to use a package we control, ngnix, instead of relying on podman being absent from the Fedora 4x base image.
• Updated Sanity workflow - I added the missing { so the entry is valid JSON again. The matrix_exclude array now parses with all 13 entries.
• Updated roles/manage_transit_gateway - updated debug message.

ISSUE TYPE

Test Pull Request

COMPONENT NAME

CI/CD workflows

Reported CI Issues

Integration tests #184

Assisted-by: Claude Sonnet 4.5 (claude-sonnet-4-5@20250929)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

I override the integration test vars, tests/integration/targets/test_deploy_flask_app/roles/run_deploy_flask_app/vars/main.yaml, — not in role defaults — so existing consumers of /tmp/id_rsa are unchanged.

[patchback]

Backport to stable-3: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply e8f35dc on top of patchback/backports/stable-3/e8f35dcd75f29b81f7487e88725252e63d716d77/pr-190

Backporting merged PR #190 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/redhat-cop/cloud.aws_ops.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-3/e8f35dcd75f29b81f7487e88725252e63d716d77/pr-190 upstream/stable-3

4. Now, cherry-pick PR ci: update integration and coverage workflow python version #190 contents into that branch:

   $ git cherry-pick -x e8f35dcd75f29b81f7487e88725252e63d716d77

   If it'll yell at you with something like fatal: Commit e8f35dcd75f29b81f7487e88725252e63d716d77 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x e8f35dcd75f29b81f7487e88725252e63d716d77

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR ci: update integration and coverage workflow python version #190 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-3/e8f35dcd75f29b81f7487e88725252e63d716d77/pr-190

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[patchback]

Backport to stable-4: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply e8f35dc on top of patchback/backports/stable-4/e8f35dcd75f29b81f7487e88725252e63d716d77/pr-190

Backporting merged PR #190 into main

1. Ensure you have a local repo clone of your fork. Unless you cloned it
   from the upstream, this would be your origin remote.
2. Make sure you have an upstream repo added as a remote too. In these
   instructions you'll refer to it by the name upstream. If you don't
   have it, here's how you can add it:

   $ git remote add upstream https://github.com/redhat-cop/cloud.aws_ops.git

3. Ensure you have the latest copy of upstream and prepare a branch
   that will hold the backported code:

   $ git fetch upstream
   $ git checkout -b patchback/backports/stable-4/e8f35dcd75f29b81f7487e88725252e63d716d77/pr-190 upstream/stable-4

4. Now, cherry-pick PR ci: update integration and coverage workflow python version #190 contents into that branch:

   $ git cherry-pick -x e8f35dcd75f29b81f7487e88725252e63d716d77

   If it'll yell at you with something like fatal: Commit e8f35dcd75f29b81f7487e88725252e63d716d77 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x e8f35dcd75f29b81f7487e88725252e63d716d77

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR ci: update integration and coverage workflow python version #190 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/stable-4/e8f35dcd75f29b81f7487e88725252e63d716d77/pr-190

7. Create a PR, ensure that the CI is green. If it's not — update it so that
   the tests and any other checks pass. This is it!
   Now relax and wait for the maintainers to process your pull request
   when they have some cycles to do reviews. Don't worry — they'll tell you if
   any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.