Activate prefer-amplify-errors

[ShadowCat567]

Problem

prefer-amplify-errors was previously inactive for the entire project, was also too sensitive and triggering on code it was not supposed to.
Issue number, if available: N/A

Changes

• prefer-amplify-errors is now active in 5 packages
• the former violation in create-amplify is now an AmplifyUserError instead of Error
• the violation in backend-deployer is suppressed until someone can take another look at it
• violations in backend-ai and backend-auth are suppressed, are not problems the linter should flag
  Corresponding docs PR, if applicable: N/A

Validation

linter is happy with the changes

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: 67999b8

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

This PR includes changesets to release 4 packages

Name	Type
@aws-amplify/backend-deployer	Patch
create-amplify	Patch
@aws-amplify/backend-auth	Patch
@aws-amplify/backend-ai	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