[spicedb] rolling update when schema changes

[svenefftinge]

Description

Ensure kubernets does a rolling update of the pods when the spicedb schema has changed

🤖 Generated by Copilot at 051abd8

This pull request enhances the SpiceDB integration by improving the logging and error handling of the authorization system, and by adding a content hash mechanism to enable rolling updates when the bootstrap configuration changes. It affects the files spicedb-authorizer.ts, deployment.go, and schema.go.

Related Issue(s)

Fixes EXP-295

How to test

Documentation

Preview status

Gitpod was successfully deployed to your preview environment.

• 🏷️ Name - se-spicedb-update
• 🔗 URL - se-spicedb-update.preview.gitpod-dev.com/workspaces.
• 📚 Documentation - See our internal documentation for information on how to interact with your preview environment.
• 📦 Version - se-spicedb-update-gha.15720

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[geropl]

Code LGTM

[svenefftinge]

/unhold