ci: automate upgrade AWS CDK

[WinterYukky]

Reason for this change

The AWS CDK version for this repository has not been updated. However, since it is inefficient for contributors to update this every time, we need automate process.

Description of changes

I implemented GitHub Actions that create a pull request to upgrade the AWS CDK version at 0 UTC every day.

Description of how you validated changes

I tested on WinterYukky/projen-auto-upgrade-cdk#2.

Checklist

• My code adheres to the CONTRIBUTING GUIDE

---

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

[mrgrain]

I don't think this is a good idea. It unnecessarily forces users to update to the latest version of aws-cdk-lib when they just want to upgrade @open-constructs/aws-cdk.

But then I also think that changing a peerDeps constraint should require a major version change. 😅

As a possible solution I can only suggest what I have suggested before: A well-define regular cycle for the release of new major versions which will include lifting the minimal version requirement to whatever is latest at that time.

[go-to-k]

Oh, we have talked about that before. FYI, I post that link for discussion @WinterYukky .

#12

[WinterYukky]

Ah, I see. That's right.
First, We should documentation about major version release schedule.