Adapt linter rules for cross repo pipelines

What does this MR do and why?

Adapt linters rules for cross repo pipelines. Initially the rational behind theses rules was to have some job always starting when we perform a cross repo pipeline, as our deployment job are manual. Otherwise we ends up with pipeline in a blocked state.

This MR revisit the rules to only start the yamllint as a minimal job. The others linters don't provide any added values as they perform their check on the sylva-core code without any modification