bugfix for wrong context path of deployed wars when context name contains dots

I detected a problem where Servlets of WARs which contain a dot in their context-name will get searched under a wrong name.
This causes headaches at our side, especially when using the `arquillian-protocol-servlet` so that I debugged the problem to understand it and implement a fix.
We have the problem with `org.jboss.as:jboss-as-arquillian-common:jar:7.2.0.Final`, which we are using, but I verified the problem exists with wildfly master, too.

Here what happens for a war named `foo-v0.3.war`:
* In `ManagementClient.getProtocolMetaData` the value of `deploymentName` is still correct, deploymentNode also contains the right information including `context-root` with value `foo-v0.3`
*  In `ManagementClient.extractWebArchiveContexts` the variable `context-name` is filled by `context-root` and still is `foo-v0.3`
* When iterating over `servletNode.keys()` the servlets get added at the wrong contextName since `contextName` already has lost its `.war` extension, but `ManagementClient.toContextName` is called which removes everything from the last do to the end.
* All Servlets get added to the wrong context name `foo-v0`
* **Bug**