build(deps): upgrade gitlab.com/gitlab-org/labkit to v1.64.10

What

Upgrade gitlab.com/gitlab-org/labkit from v1.64.8 to v1.64.10.

Why

labkit v1.64.9 split the crypto/boring probe behind boringcrypto build tags, so packages importing labkit/fips compile with -tags fips on Go's native FIPS 140-3 module (GOFIPS140) instead of requiring the boringcrypto toolchain. v1.64.10 additionally fixes SSH-algorithm registration under FIPS (not used by the registry, but it is the latest release).

The registry imports labkit/fips in registry/registry.go and registry/storage/driver/s3-aws/v2/s3.go. Registry builds do not currently pass -tags fips (they compile via labkit's notfips arm on any toolchain), so this bump is future-proofing for any fips-tag adoption plus general dependency currency, as part of the native FIPS toolchain migration epic: &22761 (closed)

Testing

With Go 1.25.12 (darwin/arm64):

• go build ./... — pass
• go vet ./... — pass
• go build ./registry/ ./registry/storage/driver/s3-aws/v2/ (the two labkit/fips importers) — pass
• GOFIPS140=v1.0.0 go build -tags fips ./registry/ — pass (fails with the crypto/boring build-constraint error on labkit < v1.64.9)
• go test ./registry/ -count=1 -short — pass

🤖 Generated with Claude Code