Review the TXBridge tests usage of Arquillian

The TXBridge tests don;t seem to be using Arquillian correctly. There is a servlet that is invoked to do things inside the container. As the tests (should) now run in the container, this should not be needed.

The tests also seem to have added complexity due to the recovery tests. As the recovery tests need to be able to kill the container, it mandates manual container lifecycle management for all tests. We may want to pull out the recovery tests into a separate module.

We also may want to pull out the DisabledContextPropagationTest into a separate module as they use a modified AS configuration.

We should also take a general look at how the tests are structured and using Arq.