Add the capability to ignore Maven2/Maven3 plugin execution errors

Description

We have a need to enable the execution of more than one instance of a container, with different deployments, during the pre-integration-test phase and then tear them down in the post-integration-phase.

Currently, in order to start, stop, configure or deploy to the same container instance from different Maven artifacts, a big chunk of the container definition needs to be copied over.

Making this an easier process requires two changes:

- Ability to start, stop, configure or deploy to the same container instance from different Maven artifacts

- To be able to ignore failures on the mojo's so that we can progress to the required stops in case something goes bad during deployment phase