312: introduce remote container development environment

[jac18281828]

closes #312

• introduces a development container with cargo and rust
• check code and rust fmt
• fix format issues currently committed on main
• tasks.json, GitHub workflow, support files etc.

[jac18281828]

I discussed this change with @insipx to ensure the workflow is correct. All checks and tests are passing. All code changes address existing formatting issues because cargo fmt is currently not checked by the ci. Check is now required as of this PR.

[jac18281828]

Added Node 20.9.0 toolchain for yarn and npm

[insipx]

I like the docker image + but adding FMT to the current workflow is better. As far as speed for 1 vs the other I'm probably not the one to know

In general I am for reproducible environments, so like the docker container and think it will make it easier to onboard devs in the future + have an easy way to get an environment up for example if we ever have a CONTRIBUTING section as the project grows. It also serves as a good enforced dependency list even if not using docker

[richardhuaaa]

To use this development container in Visual Studio Code, specify the Dockerfile as the target for the Remote Containers module

Can we include this in the README for future devs? And we mean the Dev Containers extension right?

And is it correct to say that this is optional? The alternative is to configure your environment yourself?