chore(pyproject.toml): from setuptools to uv_build as build backend

[mdevolde]

chore(pyproject.toml): from setuptools to uv_build as build backend

Why the pull request was made

As our lib is a pure-python package and expose only standard PEP 621 metadata, and doesn't implement any custom setuptools build logic, we can use uv_build as a build backend instead of setuptools to have a faster and less-configuration build backend. It is also benefic to align the build backend with the existing uv-based workflow.

Summary of changes

• Replace setuptools by uv_build as build backend
• Remove MANIFEST.in, that is now useless

Screenshots (if appropriate):

Not applicable.

How has this been tested?

By testing a build and checking what is in the tar and the wheel.

Resources

Not applicable.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (changes to documentation only)
• Refactor / code style update (non-breaking change that improves code structure or readability)
• Tests / CI improvement (adding or updating tests or CI configuration only)
• Other (please describe): chore update

Checklist

• Followed the project's contributing guidelines.
• Updated any relevant tests.
• Updated any relevant documentation.
• Added comments to your code where necessary.
• Formatted your code, run the linters, checked types and tests.