[WFLY-2321] Don't copy the file, instead just reference the existing file.

was: 9ce7b666a48f61cf78c24755ca90154da2f07697
Merge pull request #5306 from mmusgrov/WFLY-2342

[WFLY-2342] Upgrade jboss-transaction-spi

was: f5bbfe03ae7dc5c09c3d7c2f206c2ac847a2d0b6
[WFLY-490] / [WFLY-2258] Add sensitivity classification to 'describe' operation; actually enforce constraints on the READ_WHOLE_CONFIG ops

was: 9c4864922642f5f3851014e6e5b8b52817bf21b7
WFLY-490 / https://issues.jboss.org/browse/WFLY-2119 RBAC based tab-completion for the CLI (turned off by default)

was: 76f124fae86ea6be4f978a1b0444ae294eaa70ea
[WFLY-2336] The core size needs to be adjustined in line with the max size to avoid IllegalArgumentExceptions when modifying max-threads on an unbounded, queueless executor

was: 2fd8839104f908e8464ff5b24683d2af4de82597
[WFLY-2336] reorganized fix

was: ccd1e6914a286f5af8787858581ccecda2b23fa9
[WFLY-2345] Port Offset 0 does not work

When a port offset is specified in the socket binding group and the
socket binding has a port of 0, then the port offset is not used to
calculate the port instead port 0 is bound.

This pull request contains three changes:

 - fix `SocketBinding` to also do offset calculation when the port is 0

 - extend `ControllerInitializer` to allow specifing the port offset

 - add a test in `OtherServicesSubsystemTestCase`

Issue: WFLY-2345
https://issues.jboss.org/browse/WFLY-2345

was: 6d1946ff227f5c2960ba45647ed2a1b60169795e
[WFLY-2296] propagate resulting version to runtime state

was: d0959ab2455677161146de135bfc20213a484d53
[WFLY-405] improve module jar invalidation utils

was: fb68a56ab5d03c0146f00611c57d0b651a56c7b8
[WFLY-405] send rollback-to when connected

was: 93965cb8f973b235e32f4725e4b75100847fde56
[WFLY-490] / [WFLY-1852] Ensure the InetAddressPrincipal is added at the time of authentication and not retrospectively added.

was: c363d0b19a922fdd6acde2a2f019a0616a5fdac3
[WFLY-490] / [WFLY-1852] Move the access mechanism from a Principal to an operation-header

was: ea76fd12cb9a7305c5e795d9149a64f3f7f49c0c
[WFLY-490] / [WFLY-1852] Further enhancement to add an AccessAuditContext used for holding some state for the duration of the operation.

Whilst the OperationContext made a good candidate for holding some of this as soon as interaction with non-management components occurred this state was no longer accessible.
The use of a ThreadLocal here uses the Subject.doAs stye so we can ensure any previous context is cleared as the call returns up the stack.

was: 3de51331a6157c13eb820e915d886ce91067c4f3
[WFLY-2357] Use the correct check before adding runtime steps.

was: f5860e99be33c1df3cf8c9cb695146507f00ee68
[WFLY-2311] Only display the message about password validation if we actually have some verification to perform.

was: aba1680f14431803b276b982389e5f2b17d1c37d
[WFLY-1991] / [WFLY-2074] Improve how password requirements are communicated to the end user.

This change is primarily to move from outputing a list of error messages to providing a summary of the requirements - error messages are then only seen in error situations.

was: 3ee439f6e3960f4aca28b8aaa3b8925ce02c2a66
[WFLY-2373] initialize patching on slave hosts

was: 4a62c4acfed7114aa8ef2c7939af4ffd0143dbfd
[WFLY-490] / [WFLY-2337] handle additonal failed state introduced by fetching the subject

was: 38895b188c0c1a29f3c7ecdeb5292615a1d20a3a
[WFLY-490] / [WFLY-2337] send subject as part of the same request message

was: 68cd38ccaa94c321760d29493c27f29be499eb41
[WFLY-490] / [WFLY-2337] Also ensure that there is always a Subject associated with the call even if one was not provided.

was: 462e8e543b7a8a9e51e0d0123371bc2c11f8eb44