Remove obsolete license classifier

[GabrielBarrantes]

The license is already declared via SPDX (PEP 639); license Trove classifiers must not be used in that case.

See https://peps.python.org/pep-0639/#deprecate-license-classifiers

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (36ec238) to head (e814970).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #284   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          130       130           
  Branches        14        14           
=========================================
  Hits           130       130           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[GabrielBarrantes]

Probably not an issue (right now) but eventually uv_build might complain.

[palfrey]

This is only deprecated as of Metadata 2.4, which we aren't flagged as supporting yet. If we did move over to that, we should also drop License in favour of License-Expression but I'm not sure what tooling that would break...

[palfrey]

https://stackoverflow.com/questions/79363394/how-to-set-core-metadata-version-when-building-python-package indicates that most of the answer is "have a high enough setuptools version", but uncertain if there's more than that.

[GabrielBarrantes]

The issue originated because uv is still not packaged for Debian, so I used setuptools to build the package, and it failed to build because of the license classifier, just removing it fixed the problem.

About dropping the License field too, seems that is not required, as that is a Core Metadata field not a toml metadata field. The build process seems to generate those from the toml file, so is generating the classifier and (I think) the License-Expression field, altho I am not sure, I have not checked.