Dev container and documentation for GitHub Codespaces

Hi 👋

I am Samruddhi, a Software Engineer for GitHub, working with the [GitHub Codespaces](https://github.com/features/codespaces) team, and a maintainer for the [devcontainers](https://github.com/devcontainers) org 👩‍💻

[GitHub Codespaces](https://docs.github.com/en/codespaces/overview) is a cloud-based development environment that uses your dev container to provide great contributor and maintainer experiences for all users of your project 🪄

🙅‍♀️ No one would ever have to worry about setting up their local machines, adding tools/runtimes for a specific project (which most frequently contradicts with their current environment) and spend hours before even starting their actual work 🙅‍♀️

Would you be willing to accept a dev container configuration and documentation to improve the GitHub Codespaces experience? 💁‍♀️

Thanks,
Samruddhi

// cc @craiglpeters

Begin by reviewing the repository's existing contributor setup and documentation, then determine where a GitHub Codespaces dev container configuration belongs. Done means the configuration is accepted and contributor-facing Codespaces documentation is added; the issue names no files or tests, so confirm those locations with maintainers first.

Written by the indexing model from the issue text.