Allow C&C++ users to customize how and when to run the analysis

[AbbasNS]

SLVS runs the analysis on saving and files open for C++. In most cases, this is fine. But when it is not, the experience becomes unbearable, and users will not have any workaround other than uninstalling the plugin.

Some use cases where you want to disable analysis on save:

• Multiple files refactoring. Renaming a variable => x files modified => x subprocess running.
• When working with legacy code with thousands of issues, you want to fix them all without running the analysis a 1000 time
• When your laptop is low on battery, you may want to run the analysis just before committing
• When you face a performance bug-like #2798, you want to be able to avoid it while modifying the culprit file.

Describe the solution you'd like

• Option to disable analysis on save for C&C++.
• Command that appears only on C&C++ files to run the analysis
• The command should be mappable to the keyboard binding

[duncanp-sonar]

@abbas-sabra-sonarsource I see you've closed the related PR. Is this issue still required?

[AbbasNS]

@duncanp-sonar I think it is still required. I closed the PR because the PR got outdated and is probably no longer relevant.