Bump and Publish all destinations

[benmoriceau]

Destinations can now support per-stream state, with the main change being that destinations now need to keep track of the latest state message they have received and committed per-stream. Previously, destinations only needed to store the most recent state message in general, without knowing about the stream(s) involved.

We may need to re-publish all destinations to be sure that the shared base code is in use.

1. The shared database base code was updated in this PR - Update destinations to handle new state messages #13670
2. Are there any destinations that do not share the same Java base code and need to be updated manually?

We should compile a list of minimum version for each destination that supports per-stream state. This will likely need to be shared with the community in some way, probably via our docs.

[evantahler]

Note: Thanks to #13864, we can publish lots of connectors at once via a single slash command now!

[edgao]

There are a few non-java destinations (if you grep the build.gradle for airbyte-python you can find them) so they'll need manual work.

also, does the Java code update work for non-database connectors? E.g. destination-s3 doesn't use the JDBC logic at all.

[evantahler]

This Google Sheeet contains an audit of all of our destinations. It has been determined that 10 connectors need to be bumped and re-published to use the new Java destination code introduced via #13670. Most Java destinations have been published recently due to the normal flow of work.

None of the Python destinations seem to be doing anything complex with STATE messages.
They either just echo the STATE message back, or do a full flush than echo the message. Either way, there is no logic that would differ with per-stream state.

cc @sherifnada and @grishick

[evantahler]

@benmoriceau I think this story is complete? We will be re-publishing the destinations again via #14851