The actions are already lazily instantiated in
TextEditorActionHandler::setupActions(), so there should be no need to
call initializeActions() in all plugins on startup. Only the main text
editor plugin will still initialize its actions, to make sure the menu
items are there.

Accidentally reverted in commit 713105ad.
Thanks to Christian Hönig for notifying.

You can switch between sorted/unsorted via the method overview's context
menu.

Fixes: Introduce a cpp settingspage containing file naming conventions (lower case and suffixes). Reorder VCS settings pages.

Task: 241959, 248085

RevBy: Optics/Naming checked by con
Details: Give IOptionPage an id() to differentiate from trName(). Make showOptionsDialog return a bool (applied) and give it an optional parent. Change Cpp and form class wizards, give them a Configure... button to change those settings.

This stuff was all over the place, a relic from before the editor
settings were unified. Now the initialization is only done in
TextEditorSettings.

Fixes the .pro file editor and the generic project files editor, which
before only used the font settings.

I couldn't find it since it was both hidden in the cppplugin.cpp file as
well as having an unnecessarily long name.

Didn't add anything to the TextEditorActionHandler.

Details:
This patch makes use of system icons as a base
and draws overlay on top. This should blend a bit better
into the native icon theme.

Many singletons have their own instance() method, in which case there is
no need to use ICore::instance() to get access to them.

replace ExtensionSystem::PluginManager::instance()->getObject<Core::ICore>() by Core::ICore::instance()

forward declaration is sufficient.

Details:  - Naming convention

Details:  - To make it conform to naming convention.

It used to be in CppTools, but since the hover handler only makes sense
in the context of the C++ editor, this is a better place.