A while back, I switched cljdoc-analyzer from naive parsing of poms with Jsoup to loading poms via Maven (via tools.deps).

While looking at #1102, I noticed that cljdoc still naively parses POMs with Jsoup.

When we simply parse the XML of a pom, property replacement does not happen, and parent poms are not taken into account.

I'll switch cljdoc to load poms via Maven for consistency with cljoc-analyzer.

I'll likely just update the pom loading support in the cljdoc-shared repo from Jsoup parsing to Maven loading.