feat(maven): Remove unnecessary HTML page fetches

[zharinov]

Changes

It doesn't seem necessary now when we're able to obtain all necessary information by querying the corresponding POM file of a particular package version.

Context

• Ref: Maven dependency resolution performance #27768

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[zharinov]

Currently, for every package we're fetching:

• maven-metadata.xml
• GET the latest POM file (for homepage/sourceUrl)
• HEAD the POM file of the selected/filtered release (often matches with GET of the latest one)
• [Maven Central only] HTML index page

If first 3 are done correctly, seems like we don't need the latter one.

[Churro]

Currently, for every package we're fetching:

* `maven-metadata.xml`
* GET the latest POM file (for `homepage`/`sourceUrl`)
* HEAD the POM file of the selected/filtered release (often matches with GET of the latest one)
* [Maven Central only] HTML index page

If first 3 are done correctly, seems like we don't need the latter one.

If I'm not mistaken "GET the latest POM file (for homepage/sourceUrl)" is done after populating the list of releases, i.e.., any release that is unknown at this point won't be pulled. Hence, the "[Maven Central only] HTML index page" step is actually second, not last. Do you agree?

[viceice]

otherwise LGTM

[renovate-release]

🎉 This PR is included in version 39.35.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.35.0

Your semantic-release bot 📦🚀