Update the Java CDK to emit AirbyteTraceMessage

[pedroslopez]

Full context in parent issue #12322
Java connectors should emit AirbyteTraceMessage with error information when something goes wrong.

Scope / acceptance criteria:

• Implement java utility for AirbyteTraceMessage
• Implement a naive exception catch across java connectors so we can log the new AirbyteTraceMessage
  • We should propagate any existing error information up as part of this AirbyteTraceMessage, i.e. this change shouldn’t regress error usefulness.
  • To be forward compatible, check if we're catching an AirbyteTraceMessage and if so throw as is (don't naively catch)
• Write necessary tests
• Add docs to explain usage to developers
• Version bump and publish current GA java connectors
  • this will start populating filled-out FailureReasons to work with for reporting purposes e.g. for building incident management.

Not in Scope:

• Adding specific AirbyteTraceMessage errors to individual connectors
• Adding specific AirbyteTraceMessage errors to base/abstract connectors (e.g. JDBC)
• Implementing related testing (separate issue for that).

[Phlair]

Open Qs: Where do we do the naive catch?

• IntegrationRunner looks like a good contender
• Depending on the answer to this, it may become necessary to bump and publish connectors to actually implement the naive try/catch. Is that in scope?

[grishick]

@Phlair once you are done with this, could you please guide @mkhokh-33 to correctly use the new AirbyteTraceMessage in this issue

[Phlair]

@grishick absolutely, will do 👍