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

diff --git a/vendor/windows-strings/src/ref_count.rs b/vendor/windows-strings/src/ref_count.rs
deleted file mode 100644
index c6309f9f..00000000
--- a/vendor/windows-strings/src/ref_count.rs
+++ /dev/null
@@ -1,27 +0,0 @@
-use core::sync::atomic::{fence, AtomicI32, Ordering};
-
-#[repr(transparent)]
-#[derive(Default)]
-pub struct RefCount(pub(crate) AtomicI32);
-
-impl RefCount {
-    pub fn new(count: u32) -> Self {
-        Self(AtomicI32::new(count as i32))
-    }
-
-    pub fn add_ref(&self) -> u32 {
-        (self.0.fetch_add(1, Ordering::Relaxed) + 1) as u32
-    }
-
-    pub fn release(&self) -> u32 {
-        let remaining = self.0.fetch_sub(1, Ordering::Release) - 1;
-
-        match remaining.cmp(&0) {
-            core::cmp::Ordering::Equal => fence(Ordering::Acquire),
-            core::cmp::Ordering::Less => panic!("Object has been over-released."),
-            core::cmp::Ordering::Greater => {}
-        }
-
-        remaining as u32
-    }
-}