integration

We should do something like https://blog.questionable.services/article/kubernetes-deployments-configmap-change/ to ensure that if the pod sweeper has a different config map the underlying pod gets rolled.

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

We are declaring certain specific configuration required for Kaniko directly in the IntegrationPlatformBuildSpec [1] and [2]. We should not let this details slip in the general configuration. A possible alternative is to provide a PublishStrategyOptions parameter with an open array/map of parameters that can be required by the strategy used (and where to move the aforementioned Kaniko para

The package I want to suggest the idea to: AngouriMath.Interactive

The current logo includes Jupyter logo which is incorrect (since you can use that pkg in VSC Notebooks or in console etc.).

[Here](https://drive.google.com/file/d/1Y8TwuEjL0-YO2DCE6c_qs8TrhGJES_tL/view?usp=sharing