[feature][connector] JDBC sinks: support upsert and row deletion

[nicoloboschi]

Motivation

Currently JDBC sink will perform an insert query for most of the cases. The only way to execute an UPDATE or DELETE is to pass a specific property in the message properties. This is not handy and requires to all the sources to add this specific option.

The goal is to provide a way to upsert and delete records based on the record content while using key-value records.

1. Upsert: Insert or update the record based on the key fields.
2. Delete: if the value is NULL, delete the record for the given row.

Modifications

• new config option insertMode with values
  • INSERT: only perform blindly insert (default, in order to not break upgrades)
  • UPDATE: only perform blindly update
  • UPSERT: use upsert query. Main issue is that there's no SQL standard so every sink has his own implementation (by default it throws a not supported exception)
• new config option nullValueAction with values
  • FAIL: update the row with null values (default, in order to not break upgrades)
  • DELETE: delete the row with the the given key/pk

Note that in order to not break compatibility the message property ACTION has the precedence on other logics.

For the upsert mode, only the following sinks support it:

• SqlLite
• Postgres
• MariaDB

Also upgraded SqlLite to 3.36.0.3 to support upsert

others will throw an exception and the message will be rejected

• doc

[github-actions]

@nicoloboschi Please provide a correct documentation label for your PR.
Instructions see Pulsar Documentation Label Guide.

[eolivelli]

great work !