This change introduces new Prometheus metrics to provide detailed insightsinto authorization decisions, particularly for API key scopes. Thesemetrics help administrators understand why a request was allowed ordenied by breaking down the outcome.The new metrics are:- `coderd_authz_scope_enforcement_total`: Classifies each authorization  request by its outcome (e.g., scope_allow, scope_deny,  allow_list_deny) and resource type.- `coderd_authz_scope_enforcement_duration_seconds`: Measures the latency  of scope enforcement decisions.- `coderd_authz_scope_allowlist_miss_total`: Tracks requests denied  specifically due to a resource not being in a scope's allow-list.To implement this efficiently, a new `scope_metrics` rule was added tothe Rego policy. This allows the authorizer to gather detailed outcomeinformation in a single evaluation, avoiding redundant computations.The documentation for Prometheus has been updated to include details andexample queries for the new metrics.