Rework Deployer Naming Scheme

[ctrimble]

The current deployer uses subdomains to name deployed WARs. This makes it easy to find the deployer for a given URL. This reduces the amount of information that the user needs when deploying an application.

Applications deployed with the deployer also require https:// to be enabled on their APIs. This leads to a situation where we need a two levels of wildcards on an SSL certificate to share that certificate with the deployer, the deployed application, and other applications it the domain. Unfortunately, wildcard certificates can only be purchased with one level of wildcard subdomains, using SANS entries. This leads to a situation where each cadmium deployer requires its own certificate.

To get around this problem, we have been installing self signed certificates into development environments. This requires extra effort on our part, causes development environments to display messages about being not trusted, and causes issues with CORS requests in Chrome.

We need a solution that:

1. Will be easy to migrate into.
2. Supports automatically discovering a deployer, given a target URL.
3. Allows us to share a single wildcard certificate between the deployer, the deployed applications, and other applications in the same domain.