Currently the McuSupport plugin is marked as "Experimental". Experimental plugins are disabled by default, and the user can manually enable them through the plugin manager.

The SDK installer, when creating the user configuration, sets the "ForceEnabled" flag on this plugin.  This happens on the Windows installer.

The discussion so far:

1- The plugin is not experimental any more. Therefore it makes sense to remove the "experimental" flag.

2- However, in its dependencies there is the Baremetal plugin, which is still marked as experimental.  It might be wise to mark the McuSupport as "disabled by default". There is the question about whether we should update the flags for the Baremetal plugin too.

3- This plugin is only useful in the context of an installation that includes the Qt for MCUs SDK, which depends on a commercial license. We might not want it enabled by default when QtCreator is distributed as a standalone tool (e.g. through the repositories of a Linux distribution).  This supports the ide of marking it as "disabled" by default, and keep the installer feature that marks it as force-enabled in case QtCreator is installed alongside the SDK.  That would be Windows and Linux.

Conclusion:

• remove Experimental for McuSupport plugin
• plugin should be disabled by default
• Installer should force the plugin to be enabled