refactor top level cli error handling

[Amplifiyer]

Problem

1. Errors relates to credentials and access are currently marked as system faults.
2. Because of how parser's error handling was done, it was always emitting a "Success" metric in addition to a failure one during errors.

Issue number, if available:

Changes

1. Remove the yargs "middleware" error handling. Instead simply rely on try/catch to perform error handling.
2. Update FromError method to also check for CredentialsError which can happen at any aws-sdk call site and wrap it in AmplifyUserError
3. Update AccountIdFetcher to not fail when user doesn't have credentials, rather just return a dummy value for metrics.
4. Cache accountId in AccountIdFetcher for subsequent sandbox deployment runs.
5. Don't fail on failing to send metrics
6. Catch and wrap AccessDenied exceptions from sandbox

Corresponding docs PR, if applicable:

Validation

Unit tests.

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]

🦋 Changeset detected

Latest commit: 8cc4cb9

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

This PR includes changesets to release 3 packages

Name	Type
@aws-amplify/platform-core	Patch
@aws-amplify/sandbox	Patch
@aws-amplify/backend-cli	Patch

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