Prevent running services of different profiles #962
Description
With tricky combinations of elastic-package stack flags, it is possible to end up with an scenario with services started with different profiles. This can cause that some services cannot connect with the others because they are on different networks or because they use certificates signed by different CAs, as described in #959.
We could make elastic-package stack more aware of profiles, and fail when executed with a profile when there are services of other profiles running. A possible way to do it would be to check the labels of the services started, for example they will have different com.docker.compose.project.config_files and com.docker.compose.project.working_dir labels.
A more powerful alternative could be to allow to start the stack of different profiles at the same time with more isolation, but we would need to expose the ports in the host in a different way to avoid conflicts. I think that by now it'd be enough with preventing running resources of mixed profiles.