Cleanup dev setup

[mfussenegger]

• Removes buildout; test_layer now fetches the crate package itself
• Removes setup.py; there's a pyproject.toml already
• Removes stale bin/test
• Removes stale requirements.txt
• Updates DEVELOP.rst to reflect the current state - there were several oudated references.
• Removes poethepoet. Most python developers are familiar with ruff,
  mypy and pytest, no need to add an extra DSL on top that
  obfuscates what's being used.
• Removes bootstrap.sh. python -m venv or uv venv are trivial
  enough and Python developers should be familiar with them.
• Removes the devtools/create_tag.sh script. It used python setup.py --version to get the new version, which since
  Project versioning: Use versioningit #757 was broken - running
  into a chicken and egg problem: Can't read the version from git
  when about to create a new version tag. Must use git tag -s <version> instead.
• Updates the release job, which used python -m build, which wasn't
  specified as dependency anywhere. hatch is now used which uv build
  will pickup.

[mfussenegger]

Could a mac user maybe have a look at the failure?

FAILED tests/testing/test_layer.py::LayerTest::test_cluster - IndexError: list index out of range
FAILED tests/testing/test_layer.py::LayerTest::test_default_settings - AssertionError: 'http://127.0.0.1:4201/' != 'http://127.0.0.1:4200/'
- http://127.0.0.1:4201/
?                     ^
+ http://127.0.0.1:4200/
?                     ^
FAILED tests/testing/test_layer.py::LayerTest::test_environment_variables - AssertionError: 1879048192 != 314572800

Could be something odd with the teardown/port release & re-use. Can't reproduce it on my machine.

[amotl]

Could a mac user maybe have a look at the failure? Could be something odd with the teardown/port release & re-use. Can't reproduce it on my machine.

I think it's a fluke so I am just re-running the failed test case on CI, see also #404.

[mfussenegger]

I realized that requirements.txt and bin/test isn't entirely stale. Currently the doc-tests still rely on the zope testrunner.

I'm working on migrating that to use pytest too. A project shouldn't need two test runners, and their setup shouldn't be split across pyproject/setup/requirements.txt

[amotl]

Thank you for the excellent cleanup, including the removal of buildout. 💯

[amotl]

I see now that we have been able to define the CrateDB version on the test matrix before, which is no longer possible. Is it possible to bring this back?