Add devenv support and tool versions

[aug24]

What does this change?

This PR provides definition files to enable development inside a dev container.

How to test

How can we measure success?

Have we considered potential risks?

Checklist

• I have listed any breaking changes, along with a migration path ¹
• I have updated the documentation as required for the described changes ²

Footnotes

1. Consider whether this is something that will mean changes to projects that have already been migrated, or to the CDK CLI tool. If changes are required, consider adding a checklist here and/or linking to related PRs. ↩

2. If you are adding a new construct or pattern, has new documentation been added? If you are amending defaults or changing behaviour, are the existing docs still valid? ↩

[changeset-bot]

⚠️ No Changeset found

Latest commit: c7dd1e2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[akash1810]

Could we add some instructions in contributing.md detailing how one might use the dev container?

[akash1810]

Let's replace the .nvmrc file to maintain a single source of truth? I imagine the GitHub workflows would also need updating, for example:

cdk/.github/workflows/ci.yaml

Line 12 in 3a1e3a7

node-version-file: ".nvmrc"

.

[jorgeazevedo]

I think something's happened and this change was lost, but I just wanted to second this. Standardising on .tool-versions and removing all other files would be great!

[akash1810]

Are all the comments in this file necessary?

[aug24]

This is standard text that the devenv tool outputs