chore: use uv instead of poetry

[o-santi]

What kind of change does this PR introduce?

Use uv instead of poetry for python package management. This is in preparation for the coming switch to the monorepo style leveraging uv's workspace capabilities. In order to use uv workspaces, we must first ensure that supabase-py itself is working smoothly with uv.

The changes are comprised of:

1. Change pyproject.toml to use generic keywords (project, scripts) instead of poetry specific ones (tool.poetry). Most python package managers should be able to parse this information, though poetry has not implemented PEP735 compliance as of now (Support PEP 735 – Dependency Groups in pyproject.toml python-poetry/poetry#9751).
2. Rename poetry_scripts.py to cli_scripts.py, and use uv instead of poetry to run the tests. Note that uv run runs the modules inside the correct environment, so no need for extra install steps.
3. Use uv in the CI, both to run the tests, but also to build the package when publishing. This also motivated the change from the poetry_core build backend to uv_build.

What is the current behavior?

poetry is used to define the python dependencies, and to manage CI tests, and package publishing.

What is the new behavior?

uv used instead.

[coveralls]

Pull Request Test Coverage Report for Build 16652773972

Details

• 0 of 19 (0.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-2.5%) to 85.88%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
cli_scripts.py	0	19	0.0%

Totals
Change from base Build 16608740115:	-2.5%
Covered Lines:	371
Relevant Lines:	432

---

💛 - Coveralls