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

diff --git a/vendor/windows-core/src/as_impl.rs b/vendor/windows-core/src/as_impl.rs
deleted file mode 100644
index 75a8b60b..00000000
--- a/vendor/windows-core/src/as_impl.rs
+++ /dev/null
@@ -1,20 +0,0 @@
-/// A trait for retrieving the implementation behind a COM or WinRT interface.
-///
-/// This trait is automatically implemented when using the `implement` macro.
-pub trait AsImpl<T> {
-    /// # Safety
-    ///
-    /// The caller needs to ensure that `self` is actually implemented by the
-    /// implementation `T`.
-    unsafe fn as_impl(&self) -> &T {
-        unsafe { self.as_impl_ptr().as_ref() }
-    }
-
-    /// Returns a pointer to the implementation object.
-    ///
-    /// # Safety
-    ///
-    /// The caller needs to ensure that `self` is actually implemented by the
-    /// implementation `T`.
-    unsafe fn as_impl_ptr(&self) -> core::ptr::NonNull<T>;
-}