Defining conflicts in patch entries

[djacques4gorilla]

Is your feature request related to a problem? Please describe.
Maintaining a central patch list for Magento is challenging due to some conflicts with other packages, for example Magento's ECE Tools. For example, the critical PRODSECBUG-2198 patch is included in ECE Tools starting from a specific version, but would need to be applied on all projects using an older version of ECE tools or that are not on Magento Cloud (i.e. ECE tools is not installed at all). While it is possible to add the patch to the exclusion list at the project level, this has to be done manually for every project that has been updated to a version of ECE tools that includes the patch, even though this condition is known in advance.

Describe the solution you'd like
Just like it's possible to define a conflict node in a Composer file to prevent a package to be installed if another package is installed and fitting the version definition, it would be useful to have a similar node at the patch entry level to skip patches if certain conditions are met.

Describe alternatives you've considered
Alternatively, a special value in the depends node that matches if the module is not present. E.g.

"depends": {
    "magento/ece-tools": "!installed || <=1.12"
}