feat(ci): deactivate useless linter warnings for yaml document start

[Neudrino]

The document start is really a big pain and only bloats the files. This the yaml linter for it is deactivated with this commit.

This PR is required for a PR coming to add copyright headers (#13280). The PR will be opened if this one is merged, to avoid the heaps of annotations, which would be generated otherwise.

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[github-actions]

dp-workflow

0 tests   0 ✔️  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 83cf1da.

[LKreutzer]

Lgtm.

• Do you plan to re-enable the check or is it permanently turned off?
  • If it is permanent then perhaps we should clean up the document start markers and make them uniform in all files as a follow up task.

[Neudrino]

• If it is permanent then perhaps we should clean up the document start markers and make them uniform in all files as a follow up task.

Yes. This was already prepared with #13696, but could not be opened, until the first one was merged. Otherwise it would have been swamped with linter warnings. 😉