Migrate from setup.py to pyproject.toml

[hadijannat]

This pull request updates the build configuration by modifying the pyproject.toml and setup.py files to include development dependencies and refine the project setup. The goal is to improve the development environment setup and ensure consistent dependency management.

Changes:

1. pyproject.toml: Updated [build-system] requirements to include setuptools>=45, wheel, and setuptools_scm[toml]>=6.2.
   Added dev optional dependencies section to include pytest, flake8, coverage, and other development tools. Refined project metadata such as version, authors, and dependencies. Improved package data and exclusion configuration.
2. setup.py: Added extras_require section to define dev dependencies.
   Ensured compatibility with the changes in pyproject.toml.

Procedure:
CI Configuration:
The ci.yml file has been updated to use the dev dependencies during the CI pipeline runs. This ensures that all necessary development tools are installed for testing and code quality checks.
Development Setup:
To set up the development environment locally, run:
pip install .[dev]
This will install the package along with all development dependencies specified in the pyproject.toml and setup.py files.
Impact:
These changes streamline the setup process for new developers and CI environments.
Ensures that the development and testing environments are consistent across different setups.

[hadijannat]

This pull request updates the build configuration by modifying the pyproject.toml and setup.py files to include development dependencies and refine the project setup. The goal is to improve the development environment setup and ensure consistent dependency management.

Changes:

1. pyproject.toml: Updated [build-system] requirements to include setuptools>=45, wheel, and setuptools_scm[toml]>=6.2.
   Added dev optional dependencies section to include pytest, flake8, coverage, and other development tools. Refined project metadata such as version, authors, and dependencies. Improved package data and exclusion configuration.
2. setup.py: Added extras_require section to define dev dependencies.
   Ensured compatibility with the changes in pyproject.toml.

Procedure:
CI Configuration:
The ci.yml file has been updated to use the dev dependencies during the CI pipeline runs. This ensures that all necessary development tools are installed for testing and code quality checks.
Development Setup:
To set up the development environment locally, run:
pip install .[dev]
This will install the package along with all development dependencies specified in the pyproject.toml and setup.py files.
Impact:
These changes streamline the setup process for new developers and CI environments.
Ensures that the development and testing environments are consistent across different setups.

[s-heppner]

As the Python ecosystem moves toward pyproject.toml, it's often recommended to fully migrate from setup.py to pyproject.toml.
As long as there is not concrete reason not to migrate fully, I would suggest to delete the setup.py.

[s-heppner]

Can you please point this PR to eclipse-basyx/main rather than rwth-iat/main?

[s-heppner]

Can you also please update your branch, now that eclipse-basyx/basyx-python-sdk#238 has been merged?

[s-heppner]

Do we still need this PR or can it be closed with respect to the new eclipse-basyx/basyx-python-sdk#290?

[Frosty2500]

I think this PR can be closed.