Bug 885848 - Changing WAR/EAR deployment from exploded to unexploded (or vice versa) results in resource always being DOWN/Unavailable

Removed connection settings "deploymentName" attribute
Added connection settings "deploymentKey attribute (upgraded from "deploymentName")

We don't need to know if the deployment points to a "vfsfile:/" or "vfszip:/"

Now the profile service "deploymentName" is lazily loaded when the component is started or when it goes down because of NoSuchDeployment

Tested with EAP5.1.2 on WAR and EAR.
-> Deploy new package OK
-> Delete resource OK
-> Restart application OK

(cherry picked from commit 54ce392a7e2e8cc58718102f3e3af60d0ef64ab1)
Signed-off-by: Libor Zoubek <lzoubek@redhat.com>