Feature: Custom Handler groups, and handler actions config by group

[KevinJump]

At the moment handlers are placed into handler 'groups' by code - most of the default handlers are in the settings group, and content edition handlers (content, media, dictionary, domain) are in content.

The main contentious handler is the Dictionary Handler, which can sometimes be considered content and other times settings. which of these two groups it may belong to depends on your site setup and usage.

this feature update will let you change what group something is in by config

e.g.

<Handler Alias="contentTypeHandler" Enabled="true" Actions="All" Group="MySuperGroup">

If the Group setting is missing then the default group in the code will be used.

This will then change what syncs when you pick an item from the drop down in the UI.
along with this will will be adding the ability to do the default actions by group in the config .eg.

import only settings at startup:

    <ImportAtStartup Group="Settings">False</ImportAtStartup>

this won't change existing functionality (default will be ALL) - but will give people greater control over what happens when the site starts up.

[KevinJump]

A custom group will also add a custom entry to the drop down on import/report . need to consider if we will require users to add the dictionary entries for these - of if we will default to the group name, and make it up.

[KevinJump]

Still need to do the import at startup bit.