Refactor project config template engine

[j3k0]

• Adds the option to add separators within the ${...} variables.
• More ambitious goal I have in mind would be to support conditionals (will discuss this in an issue).

[j3k0]

Note, this PR was just doing some cleanup. This stuff was like copy-pasted in all different MergeProcesses.

				// Read content and inject any config parameters
				var infoAdditionsProjectContent:String = FileUtils.readFileContentAsString( infoAdditionsProjectFile );
				for (var name:String in APM.config.projectDefinition.configuration)
				{
					var regex:RegExp = new RegExp( "\\$\\{" + name + "\\}", "g" );
					var value:String = APM.config.projectDefinition.getConfigurationParam( name );
					
					infoAdditionsProjectContent = infoAdditionsProjectContent.replace( regex, value );
				}
				
				infoAdditionsProjectContent = infoAdditionsProjectContent.replace( /\$\{applicationId\}/g, APM.config.projectDefinition.applicationId );
				
				FileUtils.writeStringAsFileContent( infoAdditionsFile, infoAdditionsProjectContent );

This change was to have all that code in a single place, a helper class that implements the config-file templating engine.

Now there are some conflicts, but I'll solve them if you agree it's a valid change.

[marchbold]

I think our main concern with this one was just the naming of the class Template, I thought I mentioned it here, but must have been in a discussion. If you can clean it up and move it to something like "ConfigurationMerger" or something.

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.