Custom Cargo Tomcat container support for starting CMS/repository/plaform web application last

The default Cargo Tomcat container cannot guarantee the startup ordering of web applications because it merely copies those into the container (webapps folder and/or context.xml file copy into Catalina/localhost folder), before the container is started.

While the Cargo deployables configuration order is preserved during this copying, it cannot be relied upon how Tomcat start the web applications.

As we have specific needs for test and verification purposes (like the Configuration Verifier) to ensure the repository configuration initialization is done as a single process, we need to enforce that the CMS (or repository/platform) webapplication is always started last.

Therefore a few custom Cargo container and configuration extensions are needed, which will handle this by skipping the WAR deployable copying during the configuration phase, and then using remote deploy of the WAR deployables into the (local) running Tomcat container, with the cms/repository/plaform WAR deployed last.