Handle non-jar / metadata-only artifacts

In regards to com.github.ajalt.clikt:clikt, this is because we don’t handle non-jar dependencies yet. This dependency is metadata only, so an extension is applied during resolution. When we create our dependency query, we are not applying the classifier and extension. This causes a failure because Gradle is looking for a jar and fails.

I did find where to extract this information in #224 but never got around to adding it into the query. It’s probably very simple if you’d like to give it a shot. It should just take a little formatting magic in the query string.

_Originally posted by @ben-manes in https://github.com/ben-manes/gradle-versions-plugin/issues/334#issuecomment-688649827_

[ben-manes]

Okay, that did it. So I’ll just keep any super configuration’s external dependency that belongs to the group org.jetbrains.kotlin and both of your projects resolve. Hopefully that’s good enough for me to be inactive for another year. 😛

[sschuberth]

JCenter proxies explicit versions to Central, but not metadata queries, and can provide stale results from its cache (e.g. + resolves only on jcenter). Since that dependency is on Central only, they don’t perform the full proxying.

I’ve hijacked this somewhat related ticket, let’s see if there’s a reaction from JFrog.