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

diff --git a/vendor/unicode-width/README.md b/vendor/unicode-width/README.md
deleted file mode 100644
index 632ae159..00000000
--- a/vendor/unicode-width/README.md
+++ /dev/null
@@ -1,57 +0,0 @@
-# `unicode-width`
-
-[![Build status](https://github.com/unicode-rs/unicode-width/actions/workflows/rust.yml/badge.svg)](https://github.com/unicode-rs/unicode-width/actions/workflows/rust.yml)
-[![crates.io version](https://img.shields.io/crates/v/unicode-width)](https://crates.io/crates/unicode-width)
-[![Docs status](https://img.shields.io/docsrs/unicode-width)](https://docs.rs/unicode-width/)
-
-Determine displayed width of `char` and `str` types according to [Unicode Standard Annex #11][UAX11]
-and other portions of the Unicode standard.
-
-This crate is `#![no_std]`.
-
-[UAX11]: http://www.unicode.org/reports/tr11/
-
-```rust
-use unicode_width::UnicodeWidthStr;
-
-fn main() {
-    let teststr = "Ｈｅｌｌｏ, ｗｏｒｌｄ!";
-    let width = teststr.width();
-    println!("{}", teststr);
-    println!("The above string is {} columns wide.", width);
-    let width = teststr.width_cjk();
-    println!("The above string is {} columns wide (CJK).", width);
-}
-```
-
-**NOTE:** The computed width values may not match the actual rendered column
-width. For example, many Brahmic scripts like Devanagari have complex rendering rules
-which this crate does not currently handle (and will never fully handle, because
-the exact rendering depends on the font):
-
-```rust
-extern crate unicode_width;
-use unicode_width::UnicodeWidthStr;
-
-fn main() {
-    assert_eq!("क".width(), 1); // Devanagari letter Ka
-    assert_eq!("ष".width(), 1); // Devanagari letter Ssa
-    assert_eq!("क्ष".width(), 2); // Ka + Virama + Ssa
-}
-```
-
-Additionally, [defective combining character sequences](https://unicode.org/glossary/#defective_combining_character_sequence)
-and nonstandard [Korean jamo](https://unicode.org/glossary/#jamo) sequences may
-be rendered with a different width than what this crate says. (This is not an
-exhaustive list.) For a list of what this crate *does* handle, see
-[docs.rs](https://docs.rs/unicode-width/latest/unicode_width/#rules-for-determining-width).
-
-## crates.io
-
-You can use this package in your project by adding the following
-to your `Cargo.toml`:
-
-```toml
-[dependencies]
-unicode-width = "0.1.11"
-```