chore(deps): upgrade dependencies (projen#1905)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2431683409

------

*Automatically created by projen via the "upgrade-main" workflow*

chore(deps): upgrade dependencies (projen#1900)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2425272504

------

*Automatically created by projen via the "upgrade-main" workflow*

fix!: update GitHub actions to recent versions (projen#1890)

Update several GitHub actions vended automatically by projen to their latest versions. Several of these include major version bumps so I've marked this as a breaking change for projen.

I wasn't able to test any of the changes since I'm not aware of a good way to do so. One way might be to have some dummy repos that run through these workflows live, but that seems tricky to maintain (and keep comprehensive)...

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

chore(deps): upgrade dependencies (projen#1897)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2418515666

------

*Automatically created by projen via the "upgrade-main" workflow*

feat(github): do not create `schedule` if `cron` is empty (projen#1895)

If `schedule.cron` is empty (e.g. `UpgradeDependenciesSchedule.NEVER`), `schedule: []` is created in upgrade-main.yml.

But it shows the following error in GitHub Actions page:

```
Invalid workflow file: .github/workflows/upgrade-main.yml#L1
`schedule` accepts a list of one or more maps with the `cron` key set
```

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

chore(deps): upgrade dependencies (projen#1894)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2411937821

------

*Automatically created by projen via the "upgrade-main" workflow*

chore(deps): upgrade dependencies (projen#1893)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2406052420

------

*Automatically created by projen via the "upgrade-main" workflow*

chore(deps): upgrade dependencies (projen#1892)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2402670933

------

*Automatically created by projen via the "upgrade-main" workflow*

chore(deps): upgrade dependencies (projen#1889)

Upgrades project dependencies. See details in [workflow run].

[Workflow Run]: https://github.com/projen/projen/actions/runs/2399377230

------

*Automatically created by projen via the "upgrade-main" workflow*

feat: warn users if CDK v1 deps are installed in a CDK v2 project (pr…

…ojen#1886)

Proactively help users avoid errors by logging a warning if a CDK v1 dep has been added to the projenrc file of a CDK v2 project.

projen doesn't have a notion of "Annotations" like AWS CDK, so for now this warning is logged during the preSynthesize hook, at which point most dependencies should have been to the project's `Dependencies`.

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