Drop the versionless `License ::` classifier now that `license` is a valid SPDX expression

Ispeziona la configurazione di packaging responsabile dei METADATA generati e individua il classificatore obsoleto Mozilla Public License. Rimuovi quel classificatore mantenendo il campo di licenza MPL-2.0 esistente, quindi esegui i comandi di riproduzione di cyclonedx-bom e conferma che la licenza del componente generato contenga solo l'identificatore SPDX valido.

This issue is part of a larger batch of similar-scoped issues we distribute in the context of our internal vulnerability and dependency tracking activities. The batch covers multiple projects, this is only one of them. The goal is to rise awareness and trigger/initiate the change towards clean project metadata in projects we depend on.

Summary

This project already declares a valid SPDX license id/expression in its packaging metadata (License: MPL-2.0 in the built METADATA), but the deprecated classifier License :: OSI Approved :: Mozilla Public License 2.0 (MPL 2.0) is still present. PEP 639-aware SBOM tooling like cyclonedx-bom can't map it to an SPDX id, so it falls back to emitting the raw classifier text as a free-text license name. This free-text field is just noise and causes downstream tooling to flag this project as non-SPDX-compliant.

Suggested fix

Remove the redundant License :: OSI Approved :: from classifiers in the packaging config. No change to the license field is needed.

How to reproduce

uv tool install cyclonedx-bom
uv venv .venv-repro
uv pip install --python .venv-repro/bin/python certifi
cyclonedx-py environment .venv-repro -o sbom.cdx.json

... and then check the .licenses property of the component. There should only something like:

// This is how it should look like
...
    "license": {
        "acknowledgement": "declared",
        "id": "<VALID SPDX IDENTIFIER>"
    }
...

and not:

// This is how it should not look like
...
    "license": {
       "acknowledgement": "declared",
       "name": "<CLASSIFIER TAKEN FROM METADATA"
    }
...

I'm happy to provide a PR to resolve this timely after approval!