Use Condition internally for permissions (#1954)

<!-- The PR description should answer 2 important questions: -->

### What

Part of implementing [authorization
rules](#10237).

This pull request introduces the internals to allow type permissions to
be defined with allow / deny fields and `Condition`s that match on
session variables and literal values.

We resolve into the new auth types and use them internally for all
execution. We keep the old ones as they are used by `graphql` and
`jsonapi` schema generation.

There is no way to create clever permissions yet, these will follow.

V3_GIT_ORIGIN_REV_ID: 6212eb1cf1d94b13e24f42c6ede60ce5a1b02e58

Author: danieljharvey

v3/Cargo.lock

@@ -0,0 +1,18 @@
+[package]
+name = "authorization-rules"
+version.workspace = true
+edition.workspace = true
+license.workspace = true
+
+[dependencies]
+metadata-resolve = { path = "../../metadata-resolve" }
+hasura-authn-core = { path = "../hasura-authn-core" }
+open-dds = { path = "../../open-dds" }
+
+derive_more = { workspace = true }
+indexmap = { workspace = true }
+serde_json = { workspace = true }
+thiserror = { workspace = true }
+
+[lints]
+workspace = true