Handling uncaughtException in create-amplify command

[PG-practice]

Re-open of #2045 because I mistakenly closed it.

Problem

Issue number, if available:
#825

Changes

1. Add top level error handling with reference to similar fix top-level error handling #865
   In top-level error handling #865, parser and usageDataEmitter appears to be used for subcommands (e.g. ampx sandbox), so omit these parameters because create-amplify command are not followed by subcommands

Corresponding docs PR, if applicable:

Validation

• error_handler.ts and it's test cases are based on a similar issue fix top-level error handling #865
• Pressing Ctrl + C during Where should we create your project? prompt causes no error.

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: 416d4eb

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

This PR includes changesets to release 1 package

Name	Type
create-amplify	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

[Amplifiyer]

Instead of duplicating a lot of the code here, you can move the existing error handling from cli package to cli-core package. Both create-amplify and cli have dependencies on the cli-core package.

[Amplifiyer]

Please remove the diff for this lock file. It should not be needed for this PR.

[PG-practice]

I really appreciate your comment.
This is my first pull request, and while I struggled because I'm still learning Git and the proper procedures for modifying large products, I've tried to make the corrections.