fix(apis): use rule name in OIDC resource identifier to fix JWT authorizer attachment

[tsushanth]

Bug

When using oidc_rule with ApiOptions(security=[...]), the JWT authorizer is created in API Gateway but never attached to any route. Routes show "Authorization: NONE" despite the authorizer being visible in the Authorizers tab.

Root cause

_oidc_to_resource uses b.name as the ResourceIdentifier.name. b.name is the composite key f"{options.name}-{api_name}" (e.g. "cognito-auth-rule-auth") — used internally by _create_resource for deduplication when the same OIDC rule is applied to multiple APIs.

However, route security definitions reference the original options.name (e.g. "cognito-auth-rule"). The generated OpenAPI spec has a mismatch:

"securitySchemes": {
  "cognito-auth-rule-auth": { ... }   ← declared with composite name
},
"/logout": {
  "post": {
    "security": [{ "cognito-auth-rule": [] }]   ← references original name
  }
}

API Gateway receives an unresolvable security reference and silently ignores the authorizer.

Fix

OidcSecurityDefinition already stores self.rule_name = options.name for exactly this purpose. Change _oidc_to_resource to use b.rule_name instead of b.name:

 def _oidc_to_resource(b: OidcSecurityDefinition) -> ResourceIdentifier:
-    return ResourceIdentifier(name=b.name, type=ResourceType.ApiSecurityDefinition)
+    return ResourceIdentifier(name=b.rule_name, type=ResourceType.ApiSecurityDefinition)

The composite key in b.name is preserved for internal deduplication in _create_resource; only the identifier sent to the runtime changes to match what routes reference.

Fixes nitrictech/nitric#919