Add a threshold to only trigger downstream pipelines if the generated artifact has been deployed ("mvn deploy") or if has at least been installed ("mvn install" or "mvn deploy") or if it has been at least packaged ("mvn package" or "mvn verify" or "mvn install" or "mvn deploy").

In many cases, if a generated maven artifact has just been packaged (mvn package) or installed locally (mvn install), then we don't want to trigger downstream pipelines that have a maven dependency on this generated artifact.

Solution implemented

Add a Maven Lifecycle Phase threshold to trigger downstream pipelines ("package", "install", "deploy"). By default, withMaven will only trigger if the "deploy" lifecycle phase has been reached.