chore(deps): update reviewdog/action-yamllint action to v1.20.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
reviewdog/action-yamllint	action	minor	v1.19.0 -> v1.20.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

reviewdog/action-yamllint (reviewdog/action-yamllint)

v1.20.0

Compare Source

What's Changed

• Add fail_level and deduplicate fail_on_error by @​massongit in https://github.com/reviewdog/action-yamllint/pull/45

New Contributors

• @​massongit made their first contribution in https://github.com/reviewdog/action-yamllint/pull/45

Full Changelog: reviewdog/action-yamllint@v1.19.0...v1.20.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[village-labs-bot]

upbound/platform-ref-azure #136

Change Summary

• Updated the yamllint GitHub Action from version 1.19.0 to 1.20.0
• Updated the commit hash for the yamllint action from e09f07780388032a624e9eb44a23fd1bbb4052cc to 1dca3ad811867be18fbe293a9818d715a6c2cd46

Potential Vulnerabilities

• File: .github/workflows/yamllint.yaml:10
• Code: uses: reviewdog/action-yamllint@1dca3ad811867be18fbe293a9818d715a6c2cd46 # v1.20.0
• Explanation: While not necessarily a vulnerability, using specific commit hashes in GitHub Actions is generally good practice. However, it's important to verify that the new commit hash being updated to is from the official repository and hasn't been compromised. The update appears routine but should be cross-referenced with the official repository.

Code Smells

No code smells identified in this change. The modification is straightforward and follows good practices by using pinned commit hashes.

Debug Logs

No debug logs found in the changes.

Unintended Consequences

• File: .github/workflows/yamllint.yaml:10
• Code: uses: reviewdog/action-yamllint@1dca3ad811867be18fbe293a9818d715a6c2cd46 # v1.20.0
• Explanation: Version upgrades, even minor ones, can potentially introduce breaking changes or new behavior in the linting rules. The yamllint action's changelog should be reviewed to understand any potential changes in linting behavior that could affect existing YAML files.

Risk Score: 2

The risk is relatively low as this is a minor version upgrade of a linting tool with pinned commit hashes. The change is isolated to the CI pipeline and doesn't affect production code directly. The main consideration is potential changes in linting rules that could affect workflow.