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

diff --git a/vendor/hyper/src/server/mod.rs b/vendor/hyper/src/server/mod.rs
deleted file mode 100644
index 980553e5..00000000
--- a/vendor/hyper/src/server/mod.rs
+++ /dev/null
@@ -1,9 +0,0 @@
-//! HTTP Server
-//!
-//! A "server" is usually created by listening on a port for new connections,
-//! parse HTTP requests, and hand them off to a `Service`.
-//!
-//! How exactly you choose to listen for connections is not something hyper
-//! concerns itself with. After you have a connection, you can handle HTTP over
-//! it with the types in the [`conn`] module.
-pub mod conn;