Remove noop playbook check

[PaulFarault]

Which issue(s) this PR fixes

Fixes None

Additional comments

This check become useless. We are currently creating the list of operations from the dag and eventually assign them a playbook if define. Dag operations with no associated playbook are then treated as "noop". Hence, we are not using the noop property anymore.

Furthermore, this check doesn't cover the case where a noop is defined in collection1 and then is completed with a playbook defined in collection2.

I suggest to also remove entirely the noop property from the dag files (in the collections) are it is not used anymore.

Agreements

• I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
• I hereby agree to grant TOSIT a copyright license to use my contributions.