Improve the experience when running and debugging ServiceControl instances locally

[jpalac]

This PR alters ServiceControl to load transports and persistences from subfolders at runtime (if they are found). At startup, the installation folder (and all subfolders) are scanned for transport.manifest and persistence.manifest files. These json files contain the fully qualified type name of the class which is used to configure the transport and persistence options of ServiceControl. They also contain a human readable name for these options.

These are all loaded into an in-memory manifest. When the instance reads it's TransportType (and PersistenceType for Audit instances) setting, this is used to locate the manifest and configure ServiceControl. If no manifests are found (or they cannot be loaded) then the original behavior is used, assuming that the TransportType is a fully qualified class name.

The PR also includes a build-time step which ensures that transport and persistence artifacts are placed in subfolders under the instance build folders.

All of this means that developers working on ServiceControl can configure the app.config file in the solution to use a specific transport or persistence and start the instance under the debugger.

No changes were made to packaging, the installer, or the docker images, although all three could benefit from these changes in the future.

[ramonsmits]

Will this also be deployed with subfolders with SCMU? This would allow to 'switch' the storage engine via a config change without requiring other file/folder changes.

For example, reverting to the 3.5 would then be a manual config file change, deleting the contents of the DB Path and starting the instance and it would work. From 3.5 to 5 would not work as this requires running the setup but still relatively easy.

[mikeminutillo]

@ramonsmits This task force will probably run out of time to make these changes (and smoke test them) but that is the direction we are headed. The best use-case of this are the docker images. We currently have one image per transport but this will let us create one with all transports and select a transport at runtime via a human readable environment variable.