AS7-5584 Naming context read-only during SAR deployment

During the #start() #stop() method of a legacy SAR the naming context
is read only. The problem seems to be that
org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method) only
sets the thread context class loader and does not do
WritableServiceBasedNamingStore.pushOwner.

 - change AbstractService#invokeLifecycleMethod to take an additional
    LifecycleContext argument
  - update CreateDestroyService to pass the context
  - update StartStopService to pass the context

https://issues.jboss.org/browse/AS7-5584
AS7-5666 Transaction isolation level attribute doesn't accept integer values
JBTM-1275 Unexpected Fault type returned when participant cannot complete
AS7-5471 inbound RAR inside EAR: cannot redeploy
Update Remoting and XNIO
[AS7-5689] rewrite JBossWS remote deployer to don't leak AS7 resources
[AS7-5050] Add javax.annotation.processing to javax.api module
[AS7-5153] add sun.awt to the sun.jdk module
AS7-5679 giop-minor-version doesn't accept 0
AS7-5679 Bump the management version
[AS7-5650] Upgrade JBoss Marshalling
Remove unused version.org.jboss.marshalling.jboss-marshalling-river property from pom
AS7-2217 & AS7-5347: adding 2 new extensions of ManagedReferenceFactory, which provide support for Context#list operations and JndiView management op. The naming subsystem was changed so default safe values are returned if a factory does not implements such extensions.

updating 3 more factories, which are predefined in standalone
AS7-5687 CLI crashes with OutOfMemoryError when logging exceptions in CommandContext.handleSafe()
AS7-5701 CLI: quoting operation/command parameter values and escaping characters
AS7-5676 Propagate read-resource-description failure descriptions to the caller
JBPAPP-10134 Upgrade JSF
AS7-5600 fix test to make it work on Windows
AS7-5717 AS7.1 fix for module command fails inside a cli deployment archive
Move the version to 7.1.4.Final-SNAPSHOT