fix: e2e_amplify_outputs_backwards_compatibility only runs once, and often fails on network connectivity issues

[iankhou]

The health_checks workflow fails on the Setup baseline version due to network connectivity issues:
https://github.com/aws-amplify/amplify-backend/actions/runs/18266505828/job/52001722478#logs

Problem

There are no retries on this intermittently failing task.

Changes

Implemented retries for the task.

Validation

The workflow run on this PR will validate the change. run-e2e is applied.

Checklist

• If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
• If this PR requires a change to the Project Architecture README, I have included that update in this PR.
• If this PR requires a docs update, I have linked to that docs PR above.
• If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0844070

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[rix0rrr]

Copy/pasting a step? Can we not put a for loop somewhere?

What about other workflows that reuse the setup_base_version workflow fragment? Put the for loop inside that other workflow?