Respect dependencies declared in the POM

When uploading a JAR built with Maven (i.e., which has a POM in `META-INF/maven`), we should not only detect dependencies via bytecode scan, but also append any dependencies with runtime scope (and maybe compile scope) declared in the POM. This is important because sometimes a JAR will be a runtime dependency that is not directly referenced in bytecode, but is still necessary in some manner some discovery mechanism, reflection, etc.

Start by locating the JAR upload dependency-detection entry point and the handling of POM files under META-INF/maven. Inspect how bytecode-discovered dependencies are collected, then account for runtime and possibly compile-scoped dependencies declared in the POM. Done means required declared dependencies are appended without losing existing bytecode-detected dependencies.

Written by the indexing model from the issue text.