integration

Java and Python provide logging frameworks for recording errors and stack traces. Logging can be configured to format those messages, such as by removing newlines from stack traces, adding timestamps, and putting a log level (INFO, WARN, ERROR) on the message. In the future, it may also include json structured logging. Using the logging framew

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):

Happened quite some times with 1.5. There's a KameletBinding called timer-source-to-mysql-sink. It's deleted but then the CLI tries to remove the integration (it should not, it's automatically cleaned up).

[nferraro@localhost kamelet-catalog]$ kamel reset
1 kamelet bindings deleted from namespace camel
could not delete integration timer-source-to-mysql-sink from namespace camel: integr

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