fix: update sst to latest

[vasco-santos]

Fixes Deployment issues by finally updating to the LATEST sst and update aws cdk/sdk deps to be compatible. See migration guide for details. In reality, the core changes apply right to upgrade-guide#upgrade-to-v20, given remaining items is things we do not use today

You can run to know what versions should be used:

➜  w3infra git:(fix/update-sst-to-v2) npx sst version
SST: v2.40.3
CDK: v2.124.0
Constructs: v10.3.0

❗ while the github PR diff seems massive, actually most is on the package-lock, and changes and mostly methodical and the same things all over the place, like changing import paths

A few notes:

• srcPath was sadly removed on sst, which makes us need to use the entire path
• updated multiformats + @ipld/car dependencies because of the big changes in package-lock there were mismatch versions causing type issues in Links
• updated testcontainers given billing already had a new one and local tests were flakey because sometimes too many containers open take too long to stop/start

[seed-deploy[bot]]

View stack outputs

- **pr335-w3infra-BillingDbStack** Name | Value -- | -- customerTableName | pr335-w3infra-customer spaceDiffTableName | pr335-w3infra-space-diff spaceSnapshotTableName | pr335-w3infra-space-snapshot usageTable | pr335-w3infra-usage - **pr335-w3infra-BillingStack** Name | Value -- | -- ApiEndpoint | https://4dh0p3d5b5.execute-api.us-east-2.amazonaws.com billingCronHandlerURL | https://ca7gp67ijltxykerw2tyahb26i0hekis.lambda-url.us-east-2.on.aws/ CustomDomain | https://pr335.billing.web3.storage - **pr335-w3infra-CarparkStack** Name | Value -- | -- BucketName | carpark-pr335-0 Region | us-east-2 - **pr335-w3infra-RoundaboutStack** Name | Value -- | -- ApiEndpoint | https://xulnu4iufb.execute-api.us-east-2.amazonaws.com CustomDomain | https://pr335.roundabout.web3.storage - **pr335-w3infra-SatnavStack** Name | Value -- | -- BucketName | satnav-pr335-0 Region | us-east-2 - **pr335-w3infra-UploadApiStack** Name | Value -- | -- ApiEndpoint | https://7eqdn00vql.execute-api.us-east-2.amazonaws.com CustomDomain | https://pr335.up.web3.storage - **pr335-w3infra-BusStack** - **pr335-w3infra-FilecoinStack** - **pr335-w3infra-ReplicatorStack** - **pr335-w3infra-UcanFirehoseStack** - **pr335-w3infra-UcanInvocationStack** - **pr335-w3infra-UploadDbStack**

[olizilla]

you make it looks so easy! I thought this was gonna be much more of faff.

Do you know if sst will figure out that the stateful resources like buckets and tables are the same thing across this upgrade. Need to verify that it's not gonna try and delete and recreate them.

[vasco-santos]

Do you know if sst will figure out that the stateful resources like buckets and tables are the same thing across this upgrade. Need to verify that it's not gonna try and delete and recreate them.

yeah, that is something I pointed out to @alanshaw . We need to see what the diff will be when doing the release with seed.run in staging to be totally sure. But I would say that it won't recreate, at least from the output I see on seed.run at the moment: