Migration consequenses of Context Service ResourceDefinition attribute use-transaction-setup-provider changes

EE Concurrency 3.0 introduces ContextService customisation through context types, and one of types specified is the Transaction context, which effectively replaces the usage of the resource definition attribute named use-transaction-setup-provider (true = cleared transaction context, false = unchanged transaction context).

To prevent any conflicts we will no longer support our vendor specific config, and thus such resource definition attribute should be deprecated asap.

We should introduce new resources/attributes to configure the types of context to clear/propagate/unchange, similar to the standard Concurrency 3's ContextServiceDefinition ones. This work is a Feature Request tracked under WFLY-17912. Please note that until this is done any Context Service configured on the server config use the default ContextServiceDefinition configuration, which is cleared = Transaction (equivalent to use-transaction-setup-provider=true, i.e. any tx in the thread is suspended before and resumed after), propagated = All Remaining, unchanged = none. To use a different ContextService you need to define it on the deployment, through XML or the ContextServiceDefinition annotation.