Update @guardian/cdk, and therefore AWS sdk also

[liamness]

What does this change?

We need to move away from @aws-sdk v2 dependencies as they are EOL (see guardian/workflow#1273). Bumping @guardian/cdk will achieve this.

Had to do some fiddling to get RiffRaff to deploy using this new version, see this (reverted) commit. Might have to do that for other projects that are bumping @guardian/cdk.

How to test

Copied largely from #23:

1. Deploy the branch to CODE (we only have a CODE instance, and I've already deployed to it)
2. Open Composer CODE and load the page.
3. Enable collaborative editing feature flag and reload the page
4. Trigger a change (e.g. by editing the body) and look in your developer tools for the POST requests to https://editorial-collaboration.code.dev-gutools.co.uk
5. If it returns 200/201 or ok , it seems the changes are working
6. Also look for any error messages in the logs

How can we measure success?

No longer pulling in deprecated dependency

Have we considered potential risks?

Low level of risk as this project is not used in production

[github-actions]

Deploy build 127 of Editorial Tools::Editorial Collaboration to CODE

All deployment options

• Deploy build 127 of Editorial Tools::Editorial Collaboration to CODE
• Deploy parts of build 127 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.