Revisit resolver / package name provider #2631
Description
Today, there is a somewhat hidden behavior that takes a package and depending on the type does a few different behaviors to get a set of names which are used to search the database. This primarily is used to create the Java names of <group-id>:<artifact-id>. I believe this functionality could be moved to part of the matcher process more directly, so, for example, the Java matcher could simply call a function to get the java ID to use when it queries the database. See: https://github.com/anchore/grype/blob/main/grype/db/v6/name/java.go#L36