chore(deps): bump docker/metadata-action from 5.2.0 to 5.3.0

[dependabot]

Bumps docker/metadata-action from 5.2.0 to 5.3.0.

Release notes

Sourced from docker/metadata-action's releases.

v5.3.0

• Bump @​docker/actions-toolkit from 0.14.0 to 0.15.0 in docker/metadata-action#363 (fixes #362)

Full Changelog: docker/metadata-action@v5.2.0...v5.3.0

Commits

• 31cebac Merge pull request #363 from docker/dependabot/npm_and_yarn/docker/actions-to...
• 394bbab chore: update generated content
• ee4c905 chore(deps): Bump @​docker/actions-toolkit from 0.14.0 to 0.15.0
• See full diff 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	11		0	0.03s
✅ DOCKERFILE	hadolint	1		0	0.35s
✅ JSON	eslint-plugin-jsonc	7	0	0	2.83s
✅ JSON	prettier	7	0	0	0.52s
✅ JSON	v8r	7		0	4.09s
✅ MARKDOWN	markdownlint	3	0	0	0.91s
✅ MARKDOWN	markdown-link-check	3		0	3.85s
✅ MARKDOWN	markdown-table-formatter	3	0	0	0.22s
✅ REPOSITORY	checkov	yes		no	14.4s
✅ REPOSITORY	gitleaks	yes		no	0.16s
✅ REPOSITORY	git_diff	yes		no	0.0s
✅ REPOSITORY	grype	yes		no	13.17s
✅ REPOSITORY	secretlint	yes		no	1.66s
✅ REPOSITORY	trivy	yes		no	8.06s
✅ REPOSITORY	trivy-sbom	yes		no	3.54s
✅ REPOSITORY	trufflehog	yes		no	2.56s
✅ SPELL	lychee	32		0	0.8s
✅ YAML	prettier	13	0	0	0.97s
✅ YAML	v8r	13		0	12.2s
✅ YAML	yamllint	13		0	0.27s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[github-actions]

Test Results

16 tests  ±0   16 ✔️ ±0   41s ⏱️ +6s
  1 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 39b6533. ± Comparison against base commit 491e9f9.

[github-actions]

Pull Request Report (#234)

Static measures

Description	Value
Number of added lines	1
Number of deleted lines	1
Number of changed files	1
Number of commits	1
Number of reviews	1
Number of comments (w/o review comments)	2
Number of reviews that contains a comment to resolve	0
Number of reviews that requested a change from the author	0
Number of reviews that approved the Pull Request	1
Get the total number of participants of a Pull Request	3

Time related measures

Description	Value
PR lead time (from creation to close of PR)	1.4 Hours
Time that was spend on the branch before the PR was created	1 Sec
Time that was spend on the branch before the PR was merged	1.4 Hours
Time to merge after last review	16.6 Min

Status check related measures

Description	Value
Total runtime for last status check run (Workflow for PR)	22.8 Min
Total time spend in last status check run on PR	16.1 Min