Migrate project towards cutting edge 2025 tooling and methodology

[fkromer]

• restructure project to enable clean Python library builds
• replace poetry with uv
  • enable usage of uv workspaces
  • add CycloneDX sbom output
• pyproject.toml
  • added state of the art dev tools (test framework, static analysis, type checking)
  • single source of package build
  • single source of Python dependencies (requirements.txt files generated from it)
• fix and extend contribution docs
• remove obsolete files
• (backwards compatible Dockerfile adjustments... Dockerfile setup still not working, adding a devcontainers Dockerfile would make more sense anyways I guess... Dockerfile for report and diagram generation are usually maintained by pytm users due to "own" container security analysis tools)
• (Makefile setup not tested... is obsolete as soon as devcontainer Dockerfile is available anyways I guess)

[fkromer]

Heading towards world domination @izar 😉

[fkromer]

Merging #299 later on will be straightforward.

[fkromer]

The data contained in src/pytm/images and threatlib/threats.json needs to be considered as explicit data still potentially.