Issue with relocation of a dependency used by TransitiveDependencyCollector

[frengor]

(Didn't actually happened, but I think it's possible to encounter this)

TransitiveDependencyCollector is loaded by an IsolatedClassLoader with its dependencies already loaded.
However, maven and gradle do apply relocations also to TransitiveDependencyCollector, so relocating, for example, org.eclipse.aether to my.libs.org.eclipse.aether would break it, since the dependencies are loaded but not relocated inside the IsolatedClassLoader.

Practically, this would happen if a project which is using Libby also makes use of maven-resolver (or similar) and decides to relocate it.

[frengor]

There are two possible solution to this I think:

1. Relocate every package inside the IsolatedClassLoader, for example this method would become:

   public Library toLibrary() {
   return Library.builder()
       .groupId(groupId)
       .artifactId(artifactId)
       .version(version)
       .checksum(checksum)
       .repository(Repositories.MAVEN_CENTRAL)
       .relocate("org{}eclipse{}aether", "org.eclipse.aether")
       .relocate("org{}apache{}maven", "org.apache.maven")
       // etc etc
       .build();
   }

2. Move TransitiveDependencyCollector to another module which is NOT shaded, but published separately and then downloaded and loaded at runtime into the IsolatedClassLoader like it was a dependency. This would fix every issue with relocations, but it puts more effort into the publishing and testing process.