Separate system configuration from user configuration

The conf/*.json files are a combination of "system" configuration files that are delivered with IDM, and maintained by ForgeRock, and "user" configuration files that are expected to be modified by the user, or are unique to a sample.

For example, conf/info-ping.json - which an end user would not typically modify, but has changed between 5.0 and 5.5.

Ideally we would provide better separation. Understood this may be difficult, but we can probably improve. This would provide the following benefits:

• Easier upgrade, and less requirement for json patch files, as the system json is delivered with the IDM release bits.
• Smaller sample configurations. For example, info-ping does not need to be replicated in every sample. This also makes it easier for the user to see what is unique about the sample.
• Easier immutable container support. The set of *json files is smaller, and there is less potential for breakage between IDM releases