AWS v7 Provider upgrade

[jamesgibbons92]

AWS provider upgade has some breaking changes which requires some manual intervention before the user should deploy using the new version.
The steps are explained here https://www.pulumi.com/registry/packages/aws/how-to-guides/7-0-migration

• Upgrade pulumi to latest version (this contains the new arg flag --run-program for refresh). (Thanks to @abnud11) This will be merged separately in another PR.
• Upgrade AWS from v6 -> v7 (Thanks to @abdnud11)
• Add provider major upgrade check when running sst diff or sst deploy. Which asks the user to explicitly run sst refresh to migrate their state to the new version. Deploy/diff will be blocked until this is done and no resources in your state are using an outdated version.
• Add --run-program pulumi arg to refresh command, which allows the refresh to update the provider in the state.

[jamesgibbons92]

Draft message for release notes:

This release updates the aws provider from v6 to v7. This major upgrade contains a number of breaking changes and deprecations. Follow the guide here https://www.pulumi.com/registry/packages/aws/how-to-guides/7-0-migration/ to view the changes and update any affected pulumi aws components you may have.
There should be no breaking changes to your SST components (except for possibly any inputs you were transforming), however as part of the upgrade you must migrate your state using sst refresh before deploying with the new provider. It's advisable to also use sst diff after this command to ensure there are no unexpected changes.

[jamesgibbons92]

One thing to consider, adding support for --refresh arg to the deploy command, to automatically run refresh before deploy. This would provide a way of getting around having to do a manual refresh step before deploy and may be useful for people that have lots of stages to update.