Improving yamllint configuration

[bbaassssiiee]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind cleanup

What this PR does / why we need it:
This updates the .yamllint configuration for better compatibility with ansible-lint.
It updates all the octal-values so that they are consistently quoted.
The yamlling in the CI and pre-commit will guard this style from now on.

Which issue(s) this PR fixes:

The blessed way to write octal values nowadays is:

- ansible.builtin.file:
    path: /etc/host
    state: file
    mode: "0644"
    owner: root
    group: root

The additions for .yamllint would surface 333 errors in master, these are fixed:

333 yaml[octal-values]           basic   formatting, yaml

Reference: https://ansible.readthedocs.io/projects/lint/rules/yaml/#octals

Fixes #

Special notes for your reviewer:
Derived from the conversation in #11384

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @bbaassssiiee. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[MrFreezeex]

Thanks for splitting up the PR!
/lgtm
/ok-to-test

[bbaassssiiee]

Thanks for you patience in the review.

[MrFreezeex]

Thanks for your patience as well and for improving kubespray :D ❤️

FYI your two PRs also need an approver review so you would have to bear with us a bit more 😅

[bbaassssiiee]

🐄

[yankay]

Thanks @bbaassssiiee

A great change :-)
Could we squash the commits ,
and add the `question Does this PR introduce a user-facing change?: ' to the PR description ?

[bbaassssiiee]

Thanks! You could squash on merge, or did you imply that I rebase, sign, and signoff everything as one commit?

[bbaassssiiee]

I rebased, signed and signed-off.

[MrFreezeex]

/lgtm

[yankay]

Thanks @bbaassssiiee
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bbaassssiiee, MrFreezeex, yankay

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [yankay]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment