Move optional dependencies from dev_requirements to pyproject.toml; Introduce Hatchling Build (#268)

Co-authored-by: konstantin <konstantin.klein@hochfrequenz.de>

Author: FreddyFox892

.github/workflows/black.yml

@@ -22,7 +22,7 @@ jobs:
       - name: Install dependencies
         run: |
           python -m pip install --upgrade pip
-          pip install -r ./dev_requirements/requirements-formatting.txt
+          pip install .[formatting]
       - name: Black Code Formatter
         run: |
           black . --check

.github/workflows/python-publish.yml

@@ -35,7 +35,11 @@ jobs:
 
    build-n-publish:
      name: Build and publish Python 🐍 distributions 📦 to PyPI and TestPyPI
-     runs-on: ubuntu-latest
+     runs-on: ${{ matrix.os }}
+     strategy:
+       matrix:
+         python-version: [ "3.12" ]
+         os: [ ubuntu-latest ]
      # Specifying a GitHub environment, # Specifying a GitHub environment, which is strongly recommended by PyPI: https://docs.pypi.org/trusted-publishers/adding-a-publisher/
      # you have to create an environment in your repository settings and add the environment name here
      environment: release
@@ -45,14 +49,14 @@ jobs:
      needs: tests
      steps:
        - uses: actions/checkout@v4
-       - name: Set up Python
+       - name: Set up Python ${{ matrix.python-version }}
          uses: actions/setup-python@v5
          with:
            python-version: ${{ matrix.python-version }}
        - name: Install dependencies
          run: |
            python -m pip install --upgrade pip
-           pip install -r dev_requirements/requirements-test_packaging.txt
+           pip install .[test_packaging]
        - name: Build wheel and source distributions
          run: |
            python -m build

README.md

@@ -21,7 +21,7 @@ The framework
 - enforces users to adapt to structured and consistent patterns
 - and by doing so will lead to higher chances for maintainable and reusable code.
 
-## Architeture / Overview
+## Architecture / Overview
 The overall setup for a migration from 1-n source systems (A, B, C...) to 1-m target systems (1,2, 3...) might look like this:
 
 ```mermaid