perf: populate route match context once across entries

[rudrakhp]

Commit Message: perf: populate route match context once across entries
Additional Description: In case of multiple route entries these values are evaluated per route today which can be done only once to save compute.
Risk Level: Low
Testing: Existing tests + unit tests
Docs Changes: N/A
Release Notes: No
Platform Specific Features: N/A
[Optional Runtime guard:]
Fixes #20609

[sschepens]

doesn't this introduce aditional overhead in the case where none of these matches are being performed on routes? for example if no query param matching is used, we currently don't even parse it, we would now do so.

maybe it would be best to lazily initialize the fields of the context when needed? #20609 also suggested doing this lazily

[rudrakhp]

You’re right. I initially went with that approach, but it introduced a has() check on every access, which I was trying to avoid. That said, since the code paths that actually require all these parameters are relatively rare, we might end up with higher overhead overall from a heuristic standpoint.

[ravenblackx]

For a change whose purpose is perf, it would be nice to include some benchmark tests, and the before/after results in the PR description.