Describe the bug

We already have ways to collect and verify licenses for the Java ecosystem.

It would help a lot to also have license verification for the Python ecosystem, to ensure that dependencies are used in an ASF-compliant way.

This is rather not just an "enhancement" or "improvement" but a necessity, because I suspect that not many people will manually inspect all Python direct and indirect dependencies after every dependency change or at least before every release.

License violations cause serious trouble.

Related: #821

To Reproduce

No response

Actual Behavior

No response

Expected Behavior

No response

Additional context

No response

System information

No response