chore(jans-cedarling): optimize entity building for authorization flow performance

[dagregi]

Describe the bug
Entity building performance is causing authorization benchmarks to exceed the 1ms threshold, which will make the benchmark CI test fail.

To Reproduce

1. Run cargo bench
2. Run python3 scripts/check_benchmarks.py
3. See failures: both benchmarks exceed the 1ms threshold

Expected behavior
Authorization should complete within 1ms as defined by the performance threshold.

Additional context

• Entity building is documented here as the slowest step due to schema validation overhead.
• Another possible bottleneck that might cause benchmark failure is the constant schema lookup in context building which is already mentioned in refactor(jans-cedarling): sequential context building #11708

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Refactor jans-cedarling: Implement a new approach for entity mapping #12579

Related Issues

• fix(jans-cedarling): fix benchmarks to actually work #12900
• fix(jans-cedarling): Default entities use incorrect namespace causing validation errors #12461
• fix(jans-cedarling): fix krakend build for resource changes #11897
• feat(jans-cedarling): Implement Entity Loading and Validation System #12428

🔗 Related PRs

#12544 - fix(jans-cedarling): Fix retrieving resource entity from default entities [merged]

👤 Suggested Assignees

• olehbozhok
• unknownIoT
• 0xtinkle
• SafinWasi
• haileyesus2433

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!