Use pixi

[lvoliveira]

• Use pixi as local development tool replacing conda.
• Use pixi on CI instead of tox to keep the same tool locally on on CI
• Add lint job to ensure linting rules are being respected
• Add a build and test-build step to run on every PR instead of only run it on the deploy steps (That is run only on the tag for release)
• Modernize build to avoid calling setup.py directly. (See Why you shouldn't invoke setup.py directly )
• Remove completely broken module swagger_spec.py‎. Typing there were also completely broken.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[nicoddemus]

Nice work!

I think the documentation needs reviewing too (for example CONTRIBUTING.rst, CHANGELOG.rst, etc.)

[lincrosenbach]

Nice refactor 👍🏼

[nicoddemus]

Just to comment: in general we are moving public, standalone projects like this to uv instead, but of course pixi is OK too.

[lvoliveira]

Nice work!

I think the documentation needs reviewing too (for example CONTRIBUTING.rst, CHANGELOG.rst, etc.)

Humm, any specific suggestion? CONTRIBUTING.rst I've already updated and CHANGELOG.rst we use to update on the release-<version> branch for releasing.

[nicoddemus]

Humm, any specific suggestion? CONTRIBUTING.rst I've already updated and CHANGELOG.rst we use to update on the release- branch for releasing.

No it looks good, I missed the changes in CONTRIBUTING the first time, sorry.