chore: integrate development docker stack with vscode

[Thechi2000]

Some settings that will help development on VS Code

Closes #23

[Robb-Fr]

Great my bro

[codeofmochi]

Thank you for your additions! I've left a few suggestions. So I think we are moving towards a monorepo approach where we do bind VSCode to the devcontainer? 👍 I will open an issue for this, it would be great if we use issues systematically so that we leave a written trace for future reference (if possible, I think we should enforce that branches follow the <issue-number>-<description> naming pattern as well).

We may also want to remove the remains of the devcontainer bindings (namely the devcontainer.json files).

Edit: the issue is up at #23

[codeofmochi]

LGTM 🍔 thank you for your work. Should we cleanup the devcontainer files that we will not use anymore?

[codeofmochi]

Do you know if the "start" task is automatically stopped (sigint'd?) when VS code is closed? I think it's best if we ensure that the containers do not continue running in the background. If that is not the case, I'm not sure what we should do since there's nothing equivalent to e.g. folderClose (see microsoft/vscode#65986). Let me know @Thechi2000, thanks! 👍

[Thechi2000]

This does not seem to be possible, but it seems that reopening the folder does not launch more containers; the existing one are reattached into the task. I think we should leave it that way, since there is not much we could do

Should we cleanup the devcontainer

We can remove the unused devcontainer.json files, but the .devcontainer folders are still useful to store the Dockerfile

[codeofmochi]

I see, thank you. Though I guess since we don't use the -d flag on docker compose up anymore, when the VSCode process dies then the command may stop the stack through SIGINT? No problem anyway, we'll see how well it behaves.

[codeofmochi]

LGTM 📦 thank you!