Is your feature request related to a problem? Please describe.

Cedarling currently runs locally, which is a significant improvement over making HTTP requests for authorization. However, we want to ensure that performance remains optimal as we make changes, such as caching JWT validation results (#9913). Without proper benchmarking, we lack insight into whether our modifications improve or degrade performance.

Describe the solution you'd like

We should introduce benchmarking to measure key performance metrics, including:

• Startup time: How long Cedarling takes to initialize.
• Authorization time: The time taken to process an authorization request.

A clear and concise description of what you want to happen.

We can use the criterion crate, which provides reliable and statistically sound benchmarking capabilities, allowing us to track performance trends over time.

Describe alternatives you've considered

we can also use hyperfine but it's simpler to use criterion since it has rust macros for setting up tests.

Additional context

N/A