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, 25 deletions

diff --git a/vendor/bytes/ci/test-stable.sh b/vendor/bytes/ci/test-stable.sh
deleted file mode 100755
index ad975744..00000000
--- a/vendor/bytes/ci/test-stable.sh
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/bin/bash
-
-set -ex
-
-cmd="${1:-test}"
-
-# Run with each feature
-# * --each-feature includes both default/no-default features
-# * --optional-deps is needed for serde feature
-cargo hack "${cmd}" --each-feature --optional-deps
-# Run with all features
-cargo "${cmd}" --all-features
-
-if [[ "${RUST_VERSION}" == "nightly"* ]]; then
-    # Check benchmarks
-    cargo check --benches
-
-    # Check minimal versions
-    # Remove dev-dependencies from Cargo.toml to prevent the next `cargo update`
-    # from determining minimal versions based on dev-dependencies.
-    cargo hack --remove-dev-deps --workspace
-    # Update Cargo.lock to minimal version dependencies.
-    cargo update -Z minimal-versions
-    cargo check --all-features
-fi