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

Give users the opportunity to control the Camel K operator log verbosity via log level settings.

The setting should be added as kamel CLI option on the install command (e.g. --log-level | -v) and on the operator deployment (e.g. log-level) so users can adjust the log level on an already installed operator.

The logger framework supports V levels from 0-10. The log level setting on the op

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

• I have tried upgrading by running bundle update vite_ruby.
• I have read the troubleshooting section before opening an issue.

Description 📖

When you run a vite rake task, the [rails configuration overrides](https://github.com/ElMassimo/vite_ruby/blob/main/vite_rails/lib/vite_rails/conf