refactor: category-auth, category-geo, and category-predictions to SDK V3

[ShadowCat567]

Description of changes

Migrating:

• amplify-category-auth
• amplify-category-predictions
• amplify-category-geo

Partially migrating (some of the packages that are being fully migrated rely on functionality in these packages):

• amplify-provider-awscloudformation
• amplify-util-import

Initially was supposed to include amplify-e2e-tests and amplify-e2e-core, but they proved to be more complicated to migrate than anticipated and are being indefinitely put on hold since they are test changes and not as important as live code changes.
Also had to increase the size of the binaries.

Proxy should still work as expected, was able to add auth and geo and push while proxy was active. Attempted to update auth and geo while proxy was turned off, amplify push with the updates failed as expected.

Several e2e tests are failing on this PR that are unrelated to the SDK migrations changes:

• These tests are known to be flaky/prone to failure due to Pinpoint deprecation
  • w_notifications_sms_update_notifications_multi_env
• These tests are failing because glob dropped support for Node 18 and our Windows image still uses it, they will be fixed once we upgrade our Windows image
  • w_notifications_analytics_compatibility_in_app_2_init_e
  • w_api_7_api_10
  • w_auth_6_storage_1b
  • w_schema_searchable_apigw

Issue #, if available

Description of how you validated changes

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
• Pull request labels are added

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