Added retry mechanism to catch known errors for health checks

[vigy02]

Problem

The integration tests were failing due to intermittent errors, specifically unexpected token errors and command failures. These errors were causing the tests to fail even when they might have succeeded on a retry.

Changes

• Added a retry mechanism to the 'creates new project and deploy them without an error' test.
• Implemented a 3-minute timeout for the entire test.
• Added specific error handling for two known issues:
  1. Unexpected token '<', "<!DOCTYPE "... is not valid JSON
  2. Command failed with exit code 1: yarn add @aws-amplify/backend
• Implemented a 5-second delay between retries.
• Added logging for retry attempts and error messages.

Checklist

• [x] 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.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 8497386fb2bcdf6f5acc13b54ccfdd5f602b9587

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

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

Not sure what this means? Click here to learn what changesets are.

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