add .devcontainer setup

similar to this:
https://github.com/scicloj/devcontainer-templates/tree/main/src/scicloj

(not needed things can be removed, if needed)

->
Makes hacking on libpython-clj a bit easier.

The setup as well be re-used for a test suite with GitHub actions.
But not sure it would simplify this a lot:
https://github.com/clj-python/libpython-clj/blob/master/.github/workflows/test.yml

Devcontainer have different "philosophy". Instead of testing all JDKs, we "freeze to one".

See here for reference:
https://github.com/scicloj/clojisr/blob/master/.github/workflows/ci.yml

The tests run "inside" the same devcontainer setup then the "project" has.

首先，将 scicloj devcontainer-templates 的示例和 clojisr 的 .github/workflows/ci.yml 与 libpython-clj 的 .github/workflows/test.yml 进行比较。确定开发 libpython-clj 以及在 devcontainer 中运行其测试所需的最小设置。当仓库拥有可用的 .devcontainer 设置，并且可以使用该设置运行相关测试时，即表示完成。