Consider compiled JsonPath execution plan

[simbo1905]

JsonPath evaluation currently walks the AST directly (interpreter-style).

Question:

• Should we also provide a "compiled" execution plan (e.g., segment-specific matchers / precomputed dispatch / flattened program) to reduce per-query overhead for hot paths?

Notes / considerations:

• Public API already encourages caching the compiled JsonPath (JsonPath.parse(...)) and reusing it.
• A compiled plan could still be an internal optimization behind the existing API.
• Benchmarking should guide whether this is worth the complexity.