Revert non-shaded jdbc driver

[mosabua]

Description

The core issue the original PR attempted to address was that OpenTelemetry could not access the shaded classes correctly. However this upstream limitation is gone. OpenTelemetry is now capable of working with the shaded classes. The convention for jdbc drivers to be self-contained and not rely on additional binaries. Providing non-shaded jars encourages wrong usage of the jdbc driver and increases the complexity and surface of potential misuse, and therefore our support needs. As a result we decided to remove this again since the original need no longer exists. @electrum and @wendigo will continue to improve this and work towards pulling the client libraries into the jdbc driver and then also use those from the CLI and therefore further reduce the API exposure.

Reverting as suggested @electrum and agreed with @wendigo
Also see #23446

fyi @gaeljw

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
(x) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## JDBC

* Remove publishing a JDBC driver JAR without bundled, third-party
  dependencies. ({issue}`23452`)

[mosabua]

Somehow jdbc compatibility tests failed. I pushed again since it seems to have been a build time out.

[mosabua]

JDBC now passes. Other failures were unrelated. Merging

[ebyhr]

@mosabua Could you explain the reason in the PR description?

[mosabua]

@mosabua Could you explain the reason in the PR description?

Done .. i hope that makes enough sense.

[mosabua]

Follow up PR #23458