feat!: hooks are no longer maintained in the s3 bucket

[lazpavel]

Description of changes

• hooks files are no longer maintained in the s3 bucket -- amplify pull no longer downloads and overrides hooks directory -- amplify push / amplify init no longed uploads the hooks directory to the S3 bucket

Issue #10253

Checklist

• [x] PR description included
• [x] yarn test passes
• [x] 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

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

[lazpavel]

PR looks good , but when changing env , Do we need to pull hooks from deployment bucket ? Hi @akshbhu, CLI will no longer maintain hook files in the deployment bucket, and we'll let the customer maintain them manually or using their source control

[akshbhu]

Discussed offline

[Voyager-Two]

Using amplifyPush --simple in amplify.yml still overwrites hooks folder with the S3 bucket hooks folder (which doesn't have correct content).

[lazpavel]

Hi @Voyager-Two, can you confirm that the Amplify CLI version in the Amplify Hosting build image settings is set to latest? Thank you

[Voyager-Two]

@lazpavel Yes it's set to latest, and I've verified with build logs.

[david10e]