Add support for Github codespaces and Vscode devcontainers

I have found that it is extremely helpful dev particularity new devs to have reproducible dev environments. Github code spaces and devcontainers are a great way of supporting this.

In my fork I have gone the new dev work flow down to.

1. clone the repo
2. open in vscode and edit the .env.example file to include your foundry username and password rename to .env
3. hit the popup to reopen in a container
4. wait for the container to build
5. run npm run build
6. open foundry on http://localhost:30001 and enter admin password pf2edev

[stwlam]

Go ahead and make a PR, and we’ll look it over.

[BCNelson]

I agree that committing files for every IDE is an awful idea, that is not what I’m suggesting. Development Containers are an open standard and have tight integration with Github, this projects repository and continuous integration provider of choice.

The point of this is to lower the barrier for entry to new contributors. I think that it is hard for you to see all of the benefits as you have been working on this project regularly for a very long time. As such you are very comfortable with the current flow.

Ether way it is not a big deal for me. I can continue to use my fork with the necessary configuration changes.