[ci] add yaml files linter to pre-commit hook but skip some rules for now (Part 1)

[StrikerRUS]

First PR in series of PRs for linting yaml files.

See #6758 for background and future PRs' content required to fix all errors with the proposed config.

List of generated errors with the proposed config: https://github.com/microsoft/LightGBM/actions/runs/12383831332/job/34567296571#step:3:886.

List of available linter rules: https://yamllint.readthedocs.io/en/stable/rules.html.

Won't merge this PR without reviews from @borchero and @jameslamb (#6758 (comment)).

[jameslamb]

Thanks for working on this! I just proposed a different approach, would like to hear your thoughts.

[jameslamb]

This will be a bit disruptive to local development.. running pre-commit run --all-files locally (which I do many times during local development)... will produce a lot of output and fail until we've fixed all the issues.

Would you consider the following instead?

• add all the rules that currently produce errors to .yamllint.yml in this PR with :disable
• remove the SKIP=yamllint in lint-python-bash.sh
• enable more and more rules over each of the next set of PRs.

That would prevent any new issues from being introduced on master while allowing pre-commit run --all-files to continue working locally.

[StrikerRUS]

Makes sense! Thank you very much for the suggestion! I just pushed 4adf207 with these changes.

[StrikerRUS]

@borchero Could you please take a look when have time?

[jameslamb]

Thank you!

[StrikerRUS]

Trying to close-reopen for Azure restart.

[borchero]

LGTM! The approach outlined by @jameslamb (i.e. enable more rules in follow-up PRs) makes a lot of sense to me :)