Treat maven artifact with `relocation` entry as the same package

[BenWoodworth]

Is your feature request related to a problem? Please describe.
Maven artifacts that have been relocated appear as separate entries under a project's packages.

---

Describe the solution you'd like
Consider the relocated package as an earlier version of the package at the new coordinates, avoiding both entries being listed on a project.

When looking to see if an artifact is KMP, the relocated artifact won't have kotlin-tooling-metadata.json if the library author followed Apache's relocation guide, so following to the new artifact's location and checking there for the metadata might be necessary.

---

Describe alternatives you've considered
Alternately, maybe a warning/tooltip could be shown, saying that it's been relocated. The relocation entry has an optional message, so that could be used.

---

Additional context
My Parameterize library's main dependency moved from parameterize to parameterize-core in v0.4.0. Now the Packages tab lists both parameterize-core:0.4.0 and parameterize:0.3.3 (even though there is parameterize:0.4.0 that's a relocation).

[dkrasnoff]

Hi Ben Woodworth (@BenWoodworth), thanks for your feedback.

At the moment, I'm not certain about the technical solution. We currently don’t process artifacts that lack a *-kotlin-tooling-metadata.json file, and as far as I can see, parameterize-core doesn’t include any information about the original artifact from which it was relocated.

That said, I’ve added your request to our internal backlog for future investigation.