add devcontainers configuration

[johannesjh]

suggestion to add a devcontainers config to this repo.

Motivation: A devcontainers configuration would allow contributors to develop and build fava without having to mess with package installations on the local machine.

Specific example configuration: The following devcontainers configuration worked fine when I gave it a try.

// For format details, see https://aka.ms/devcontainer.json. For config options, see the
// README at: https://github.com/devcontainers/templates/tree/main/src/debian
{
	"name": "Debian",
	"image": "mcr.microsoft.com/devcontainers/base:bullseye",

	// Features to add to the dev container. More info: https://containers.dev/features.
	"features": {
		"ghcr.io/devcontainers/features/python:1": {},
		"ghcr.io/devcontainers/features/node:1": {}
	},

	// Install additional packages as needed
	"postCreateCommand": "pip3 install --user build twine"

	// Use 'forwardPorts' to make a list of ports inside the container available locally.
	// "forwardPorts": [],

	// Configure tool-specific properties.
	// "customizations": {},

	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
	// "remoteUser": "root"

}

[yagebu]

Thanks for the suggestion, but I'm hesitant to add configuration for tooling that seems to firmly sit in the proprietary (and mainly Microsoft) world (e.g. on https://containers.dev/supporting, only proprietary editors are listed).

develop and build fava without having to mess with package installations on the local machine.

With a virtual env, there's not really any need to mess with package installations (or at least not more than necessary to get Docker / devcontainers up and running).