[WFLY-4172] Enable the -secmgr parameter for tests if the security.manager property is defined.

I left these commits separate as they seemed to make more sense that way. I can squash them together or squash specific ones together if that seems to make more sense.

### Commit f31a0086b973d283afae585c43ccb554e552ca7b
This is the main commit for the JIRA and simply enables the testsuite to enable the security manager by passing `-Dsecurity.manager` to the build.

Note that a dummy property is passed in the `<jboss.args/>` property defined in the parent test suite pom. If left blank system property is set to `null` which in when parsed by arquillian becomes `${jboss.args}` as that's the argument in the arquillian.xml file.

### Commit 64e510b8df95ca2499c195e63f3d5c58bbb8dd0d
Enables the security manager extension by default for all server types.

### ba3f549e705a9d696214aeb4284809d5ec2f9c51
Runs the `NamingContext.bind()` in a privileged block as the permissions have already been checked.

### Commit c7283537e0ba1bd44acf5986f583e72b7f3e0628
Fixes some issue found with generating the permissions.xml for deployments.

### Commit 2012f933ce27bd630f3a9e20a43537f254af5a45
Fixes a few issues found when running the web integration tests under the security manager.
This should be AccessController.doPrivileged rather than doUnchecked(). Do unchecked runs everything in the block with the security manager disabled. Theoretically code could create a new NamingContext with a custom NamingStore that will then be run with no permission checking enabled. If you use doPrivileged instead this is not possible, as the permissions will be limited to the permissions of the code source of the custom naming store.