feat: Add an option to disable the CloudFront invalidate on deployment

This reddit post describes the issue quite well: https://www.reddit.com/r/aws/comments/kak4l7/aws_amplify_keep_artifacts_from_old_builds_live/

We could solve this by simply skipping the cache invalidation step after a deployment. That should be an option to configure for each project or branch.

Start by tracing the deployment flow to the CloudFront cache invalidation step and review how project and branch settings are configured. Done means a project or branch can explicitly skip invalidation after deployment, while the default behavior remains clear and the option is covered by the relevant deployment tests.

Written by the indexing model from the issue text.