Optimize Router matching with prefix Trie filter (#509)

This commit replaces the (N)$ linear route iteration with a fast-path Trie filter.
Instead of checking every registered route's RegExp against the incoming request,
the Router now builds a prefix tree using the literal, non-variable segments of each route.

When a request is received, the Router walks the Trie to collect only routes
that exactly match the static prefix of the request path. It then evaluates
the original RegExp match only on those isolated candidates.

This provides (L)$ routing candidate filtration for massive APIs while maintaining
100% exact backward compatibility (preserving exact regex extraction, nested routers,
and exact positional priority).

Performance Metrics (10k routes across 100 controllers):

| Metric | Before (Linear) | After (Trie) | Speedup |
| :--- | :--- | :--- | :--- |
| Worst-Case Match | 902.19 μs | 3.20 μs | ~281x Faster |
| 404 (Not Found) | 734.12 μs | 0.45 μs | ~1,631x Faster |