Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

Tell us about the problem you're trying to solve

A connector is an evolving piece of software. We want to set the proper expectations for an Airbyte user when using a connector.

Describe the solution you’d like

When selecting a connector, a user should see if it is an early, not super tested connector or very mature one (# of levels to be defined).

Setting logging.level.org.apache.camel=DEBUG does not affect integration logs.

So if users set flag --logging-level org.apache.camel=DEBUG, that is currently translated into the property above and does not work.

The correct mapping should be something like: quarkus.log.category."org.apache.camel".level=DEBUG

We should also change the doc to point to the Quarkus documentation for con

Is your feature request related to a problem? If yes, please describe the problem.
Currently our playground is without any code sharing capabilities.

Describe the solution you'd like to see.
Allow to share the playground with a certain query by adding the query as a base64 in the URL.

Were you inspired by anything else, that you have experienced?
Inspired by https://sandcastle