Gradle refactoring

[planetf1]

Initial PR for refactoring of gradle dependencies

• Uses shadow plugin for building uber jars
• Moves version specs to dependency constraints
• updates plugin versions
• Ensures project/build health run for both projects
• removes most tasks from top level project - no need to publish it
• cleans up dependencies as reported by dependency analysis plugin

Caveats

• Ideally we'd depend on the egeria BOM, but this is currently broken for v4

  Todo

  • identify runtime dependencies for migrator (any additional to core connector?)
  • test connector & migrator

[planetf1]

The platform spec can now be imported following availability of https://github.com/odpi/egeria/issues/7499 Note that currently there are dependency constraints that can now be removed

@cmgrote can you advise how I should test. Anything needed beyond what we currently have in gradle (at least for now)

If not can you take a look at the changes and see if they make sense?

I can finish the gradle cleanup in this, or a later PR -- keen to get this merged and test in the automated cts (xtdb currently failing as we know due to the v4 changes)

[planetf1]

I am proposing to merge this late today or tomorrow so that we can validate the new BOM support for v4, and have the automated CTS run against XTDB - there may be further work on all of these & we're approaching branch time for r4 in about a week.

The changes proposed are packaging only (of course that affects runtime)

[cmgrote]

Makes sense to me — if you can just confirm on the question I raised above (assuming this doesn't pull in all those dependencies), let's go ahead and merge. I won't have a chance to do much of a deeper review over the next couple of days.

[planetf1]

I am aware the aggregate javadoc is broken. Will fix as I test the connector works with 4.0 .. later this week.

I had missed checking that