Clear up use of ProfileName, not the same as ProfileKey in ProfileService

profileName is used in Managed and Embedded to specify which server profile (directory) to use; "default", "standard", "all", etc

Later the same value is used to load the ProfileService profile.

profileName is used with Remote to specify which ProfileService profile to load.

This is wrong. The ProfileService Profile is either "deployments", "deployers" or "farm", referring to the directory within the server profile(+ how to install them in MC).

From Arquillians point of view, the ProfileService Profile should always be "deployments", and the profileName configuration option can be removed from the Remote containers.