Do not trigger capm3 pipeline on renovate::configuration label

What does this MR do and why?

For renovate MR (updates we want to trigger automatically a capm3 pipeline), but for renovateconfiguration we don't need that as most of the time theses MR have zero impact on the deployment.

This MR fix that , and save some CI resources

Edited by Loic Nicolle

Merge request reports

Loading