[Snyk] Security upgrade alpine from 3.15.0 to 3.16.9

[vroldanbet]

This PR was automatically created by Snyk using the credentials of a real user.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Changes included in this PR

• Dockerfile

We recommend upgrading to alpine:3.16.9, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Some of the most important vulnerabilities in your base image include:

Severity	Priority Score / 1000	Issue	Exploit Maturity
	179	CVE-2022-28391 SNYK-ALPINE315-BUSYBOX-2440607	No Known Exploit
	179	CVE-2022-28391 SNYK-ALPINE315-BUSYBOX-2440607	No Known Exploit
	184	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-ALPINE315-OPENSSL-3314622	No Known Exploit
	184	Access of Resource Using Incompatible Type ('Type Confusion') SNYK-ALPINE315-OPENSSL-3314622	No Known Exploit
	240	Out-of-bounds Write SNYK-ALPINE315-ZLIB-2976173	No Known Exploit

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Access of Resource Using Incompatible Type ('Type Confusion')

[vroldanbet]

@jzelinskie I updated the CLA assistant automation here to be aligned with SpiceDB's definition, and I also updated the centralized action to use the latest GHA action, still it seems to be complaining about a missing token. Does it ring a bell? Could you audit the repo credentials? (I presume you set it up)