Adding devcontainer

[matteogrechi]

Personally I prefer to work in devcontainer to keep my machine clean of development dependencies and settings.

[mcharytoniuk]

@matteogrechi Sorry I didn't take a look at the PR sooner. I am working on setting up Paddler in prod with our new service, and I didn't have time to test the devcontainer. You can leave the PR open I will take a look at it in the next few weeks probably.

[Propfend]

Thanks for using paddler and contributing to this project. A development setup is fine, but there are some caveats to consider:

• CUDA toolchain is relatively big download. It probably would be better if the dev-cuda13.dockerfile file was split into two or more, where one has the necessary toolchain to run project with CPU-only support, otherwise someone who does not want to use the GPU features or doesnt have hardware which support that would be stuck to that and wait a lot.
• That said. Would be nice as well to have an option for Vulkan. But i appreciate your help with CUDA.
• The fact this is coupled to code editors like VS code of sorts is not so good. Sure, we can do docker build --file .devcontainer/dev-cuda13.dockerfile but we could have something which can have layer of support to multiple systems, so we wouldnt be tied to that. Or let user decide what they want to use, like a devcontainer with a .gitignore inside. Wouldnt something like Devbox or something fit better? It is essentially a shell.