Gather data around unknown licenses for Maven in license-db
Problem statement
Currently we are lacking a monitoring infra to figure out which Maven package licenses appear as unknown.
Proposal
As investigated in #441180 (closed) there are many Maven license strings that can lead to an unknown license. The reasons can vary. For example it could be that is not an SPDX license, or it is an SPDX license but there is a missing license. The idea here is to store information in the following format:
license string, package
The data can be either exported in a bucket, or published on another service for post processing and storage or even use Prometheus for this. We need to investigate which approach is the most boring.
Related issues
Extra "unknown" reported for some packages (#441180 - closed)