Embedded API is confusing re process types

EAP note: This is an issue in the API exposed by the private 'embedded' module, so it's really an internal thing in EAP 7.0. But I'd like to clean it up for WildFly 10.0.0.Final, as in upstream this API is available to users, including the ARQ intergration. Also, it's possible at some point in EAP 7.x we may wish to support this at some level so it's better to get it clean now.

The embedded API has gotten a bit confusing with respect to names and types, primarily the use of the word "server" in a number of placing where the relevant thing could either be an embedded standalone server or an embedded host controller. So to correct this:

Deprecate the EmbeddedServerFactory class, the primary API for embedded. Introduce a new factory class EmbeddedProcessFactory to replace the now deprecated EmbeddedServerFactory. Deprecated EmbeddedServerReference, and introduce a new EmbeddedManagedProcess interface as the super-interface for the existing StandaloneServer and HostController interfaces, thus unifying their APIs in a cleaner way than EmbeddedServerReference. Subclass ServerStartException with EmbeddedProcessStartException and then deprecate the superclass.