Implement an unit/integration test strategy

Due to the need to separate integration from unit tests, we introduced a
new test strategy. To achieve this goal, we're using TestNG's grouping
capabilities (http://testng.org/doc/documentation-main.html#test-group):

To create an unit test, a test developer has to write their test method
(or entire test class) without any group annotation.

To create an integration test, a test developer has to use the custom
"it" group for his test method (or test class).

For more information on integration test possibilities see:
http://maven.apache.org/surefire/maven-failsafe-plugin/index.html
Change JavaSecVerifierTest to an integration test
Disable Findbugs for test classes
Don't use the RefreshAddress in case the CommunicationErrorAddress is not available.

Also don't check for a https URL in the TCToken class this is already done in the TCTokenVerifier.
Furthermore renamed the methods name to get the CommunicationErrorAddress with the required
query parameters.
Use method which adds the error query parameters to the communicationErrorAddress.
Close connection after the paos communication.
Improvement of exception handling and show error or success messages to the user.
Make EAC GUI displayed longer and cancelled in TCTokenHandler
Mark StreamHttpClient test as integration test