build: add devcontainer setup

[havogt]

No description provided.

[egparedes]

Just a couple of suggestions to use uv:

[egparedes]

Can we also add some basic python tooling like pipx & uv? For example:

Suggested change

	&& export DEBIAN_FRONTEND=noninteractive && apt-get install -y libboost-dev \
	&& apt-get clean && rm -rf /var/cache/apt/* && rm -rf /var/lib/apt/lists/* && rm -rf /tmp/*
	&& export DEBIAN_FRONTEND=noninteractive && apt-get install -y libboost-dev \
	&& apt-get install pipx && ensurepath && pipx install uv \
	&& apt-get clean && rm -rf /var/cache/apt/* && rm -rf /var/lib/apt/lists/* && rm -rf /tmp/*

(the pipx installation assumes the base image is a reasonably recent Ubuntu version: https://pipx.pypa.io/latest/installation/#on-linux)

[egparedes]

If we install uv in the dockerfile then we can use it here which should be nicer and much faster:

Suggested change

	python -m venv .venv
	source .venv/bin/activate
	pip install --upgrade pip setuptools wheel
	pip install -e .
	pip install -r requirements-dev.txt
	pip install -i https://test.pypi.org/simple/ atlas4py
	uv venv .venv
	source .venv/bin/activate
	uv pip install -r requirements-dev.txt
	uv pip install -e .
	uv pip install -i https://test.pypi.org/simple/ atlas4py

[havogt]

Should we just --user or --system install instead of venv? Since the devcontainer is anyway an isolated environment...

[egparedes]

Should we just --user or --system install instead of venv? Since the devcontainer is anyway an isolated environment...

Yes, I agree. I don't think we need a venv inside the container