Dependency resolution fails for high level rest client and JDBC driver on version 7.13.0

[mark-vieira]

Looks like some fallout from #69027 caued the POMs generated for any shaded jars (just the HLRC and JDBC driver) to include all the shaded dependencies. This causes issues when trying to resolve these artifacts as some of the referenced dependencies aren't published anywhere.

The root cause seems to be use register the vanilla Gradle Java component to the publication rather than the shadow component. I think we avoided this due to configuration ordering problems so instead we might need to define a separate publication for shadow projects, or override the existing "elastic" publication completely.

[elasticmachine]

Pinging @elastic/es-delivery (Team:Delivery)

[mark-vieira]

@elastic/infra-release I believe we had a mishap like this before and were able to retroactively publish updated pom files? We might want to consider doing that again here. The actual artifact is fine, it's just the POM that's busted.

[mark-vieira]

Ok, so we still want to fix this but it isn't as bad as I had initially thought. So the JDBC driver indeed fails, but in practice, most folks don't actually consume that artifact via Maven/Gradle dependency resolution. They just download the JAR for use by their BI tool of choice. The HLRC does resolve (since all of it's dependencies are publicly published), but you just end up bringing a whole boat load of duplicate JARs.

[mark-vieira]

Resolved by #73467.