Segregate integration tests in docker executor
What does this MR do?
It segregates the integration tests from the docker package into a different file (so it can be easily tagged later) and package (so we know that it doesn't leverage internal aspects of the tested package).
Why was this MR needed?
Integration tests are currently mingled with unit tests, making it difficult to know where to add a new integration test, or for example to run only unit tests ignoring integration tests.
What's the best way to test this MR?
Check that moved tests still execute in the CI job, e.g.: