GH-802: Reimplement URL handling by decorating input streams with commons-compress

[ascopes]

This reimplements all the low-level URL handling logic internally to remove the SPI workaround that is currently in place, and use a recursive dispatcher that has custom URLStreamHandlerFactories associated with it. These implementations can delegate to archivers and compressors in Apache commons-compress to provide support for protocols such as 'tar:gz:https://...'.

This effectively allows users to utilise arbitrary tarballs as the source of their plugins now rather than just JARs.

Current implementation provides:

• Archivers for 'jar', 'war', 'ear', 'kar', 'zip', 'tar'
• Compressors for 'gzip', 'bz2'

We can add further integrations such as 'xz', 'cpio', 'ar', 'ar2', 'lzma', '7z', 'deflate', 'z', 'zstd', etc as needed by appending to the list of providers in the new UrlFactory.

TODO:

• This has currently only been tested using tar.gz to prove that nested retrieval works as expected. Other implementations will still need unit tests to be added.
• The tests for UriResourceFetcher are now invalid and need a full rewrite to handle delegating to this new mechanism under the hood.
• Unit tests for new classes.
  • URLConnection wrapper classes
  • Integration with file protocol for UrlFactory
  • Integration with http(s) protocols for UrlFactory
  • Test cases for each scheme in each archive protocol we support
  • Nested archive test cases
• Documentation needs updating with new examples in the plugin Mojo javadocs.
• Documentation in the user guide needs updating.
• Minor version bump or major version bump.
• Set @since tags in new classes.
• Check if we need to propagate timeouts, useCaches, etc to nested connections.

---

If possible, help is needed to verify this against existing behaviour in real world use cases to help ensure no new edge cases exist. If this is something that is of interest, please comment on this PR. If any semantic changes are spotted, this may need to be a breaking change and be part of a newer major version instead. Hopefully that will not be the case.

---

Closes #802.

Covers #722, #795 (for the core use case, further elaboration on other points may be needed elsewhere but those should be a new issue once confirmed).

[codecov]

Codecov Report

❌ Patch coverage is 85.95041% with 17 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.11%. Comparing base (1cc5f4a) to head (74eb43c).
⚠️ Report is 8 commits behind head on main.

Files with missing lines	Patch %	Lines
...urls/AbstractRecursiveUrlStreamHandlerFactory.java	76.79%	9 Missing and 4 partials ⚠️
...venplugin/urls/ArchiveUrlStreamHandlerFactory.java	83.34%	2 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #803      +/-   ##
==========================================
- Coverage   91.61%   91.11%   -0.49%     
==========================================
  Files          60       63       +3     
  Lines        1811     1901      +90     
  Branches      121      129       +8     
==========================================
+ Hits         1659     1732      +73     
- Misses        114      125      +11     
- Partials       38       44       +6     

Files with missing lines	Coverage Δ
...protobufmavenplugin/mojo/AbstractGenerateMojo.java	100.00% <ø> (ø)
...enplugin/mojo/ProtobufMavenPluginConfigurator.java	100.00% <ø> (ø)
...tobufmavenplugin/plugins/BinaryPluginResolver.java	63.64% <ø> (ø)
...pes/protobufmavenplugin/protoc/ProtocResolver.java	65.00% <ø> (ø)
...otobufmavenplugin/sources/ProtoSourceResolver.java	80.96% <100.00%> (ø)
...plugin/urls/DecoratingUrlStreamHandlerFactory.java	100.00% <100.00%> (ø)
...s/protobufmavenplugin/urls/UriPlexusConverter.java	100.00% <ø> (ø)
...s/protobufmavenplugin/urls/UriResourceFetcher.java	100.00% <100.00%> (ø)
...b/ascopes/protobufmavenplugin/urls/UrlFactory.java	100.00% <100.00%> (ø)
...venplugin/urls/ArchiveUrlStreamHandlerFactory.java	83.34% <83.34%> (ø)
... and 1 more

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ascopes]

I need to have a further think about how the URL bits and pieces are tested. Regardless, I am happy enough with how that part of it is tested via ITs currently, so I'm going to merge this for now and see how it goes.