[backport] build(deps): Bump crazy-max/ghaction-docker-meta from 5.8.0 to 5.9.0 in the actions-deps group (#1174)

[mergify[bot]]

Bumps the actions-deps group with 1 update: crazy-max/ghaction-docker-meta.

Updates crazy-max/ghaction-docker-meta from 5.8.0 to 5.9.0

Release notes

Sourced from crazy-max/ghaction-docker-meta's releases.

v5.9.0

• Add tag-names output to return tag names without image base name by @​crazy-max in docker/metadata-action#553
• Bump @​babel/runtime-corejs3 from 7.14.7 to 7.28.2 in docker/metadata-action#539
• Bump @​docker/actions-toolkit from 0.62.1 to 0.66.0 in docker/metadata-action#555
• Bump brace-expansion from 1.1.11 to 1.1.12 in docker/metadata-action#540
• Bump csv-parse from 5.6.0 to 6.1.0 in docker/metadata-action#532
• Bump semver from 7.7.2 to 7.7.3 in in docker/metadata-action#554
• Bump tmp from 0.2.3 to 0.2.5 in docker/metadata-action#541

Full Changelog: https://github.com/docker/metadata-action/compare/v5.8.0...v5.9.0

Commits

• 318604b Merge pull request #539 from docker/dependabot/npm_and_yarn/babel/runtime-cor...
• 49c0a55 chore: update generated content
• 486229e Merge pull request #558 from crazy-max/fix-dist
• f02aeab chore: fix dist
• beafb97 chore(deps): Bump @​babel/runtime-corejs3 from 7.14.7 to 7.28.2
• 3ff819c Merge pull request #557 from crazy-max/yarn-4.9.2
• 05838e9 update yarn to 4.9.2
• 43fa4ac Merge pull request #556 from crazy-max/dev-deps
• b3120f2 chore: update generated content
• 1f469d2 update dev dependencies
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

---

This is an automatic backport of pull request #1174 done by [Mergify](https://mergify.com).

[mergify[bot]]

❗❗❗ All commits in this PR must be signed off. Please sign all commits by:

git rebase HEAD~1 --signoff
git push --force-with-lease origin mergify/bp/release/v1.6/pr-1174

[mergify[bot]]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Enforce verified commits

This rule is failing.

Make sure that we have verified commits

• [ ] #commits-unverified = 0

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• [X] title ~= ^(\[wip\]|\[backport\]|\[cherry-pick\])?( )?(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?:

🟢 Enforce linear history

Wonderful, this rule succeeded.

Make sure that we have a linear history, no merge commits are allowed

• [X] linear-history