feat: migrate from Cedar to SpiceDB authorization system

This is a major architectural change that replaces the Cedar policy-based
authorization system with SpiceDB's relation-based authorization.

Key changes:

- Migrate from Rust to Go implementation
- Replace Cedar policies with SpiceDB schema and relationships
- Switch from envoy `ext_authz` with Cedar to SpiceDB permission checks
- Update build system and dependencies for Go ecosystem
- Maintain Envoy integration for external authorization

This change enables more flexible permission modeling through SpiceDB's
Google Zanzibar inspired relation-based system, supporting complex
hierarchical permissions that were difficult to express in Cedar.

Breaking change: Existing Cedar policies and Rust-based configuration
will no longer work and need to be migrated to SpiceDB schema.

1 files changed, 0 insertions, 30 deletions

diff --git a/vendor/regex-syntax/test b/vendor/regex-syntax/test
deleted file mode 100755
index 8626c3bf..00000000
--- a/vendor/regex-syntax/test
+++ /dev/null
@@ -1,30 +0,0 @@
-#!/bin/bash
-
-set -e
-
-# cd to the directory containing this crate's Cargo.toml so that we don't need
-# to pass --manifest-path to every `cargo` command.
-cd "$(dirname "$0")"
-
-# This is a convenience script for running a broad swath of the syntax tests.
-echo "===== DEFAULT FEATURES ==="
-cargo test
-
-features=(
-    std
-    unicode
-    unicode-age
-    unicode-bool
-    unicode-case
-    unicode-gencat
-    unicode-perl
-    unicode-script
-    unicode-segment
-)
-for f in "${features[@]}"; do
-    echo "=== FEATURE: $f ==="
-    # We only run library tests because I couldn't figure out how to easily
-    # make doc tests run in 'no_std' mode. In particular, without the Error
-    # trait, using '?' in doc tests seems tricky.
-    cargo test --no-default-features --lib --features "$f"
-done