Construct JSON path only on exceptional cases.

[guidobrei]

This pull request addresses issue #63: Excessive object and memory allocations from string format operations during JSON logic evaluation.

Summary of Improvements

• Optimized jsonPath Construction:
  Now, jsonPath is built only when exceptions are thrown, not on every evaluation step.
• Reduced Usage of String.format:
  Frequent string formatting—previously responsible for a large portion of memory allocation—is now minimized.
• Efficient String Manipulation:
  Refactored string handling within the evaluation logic for improved efficiency.
• Decreased Unnecessary Object Creation:
  Memory profiles should reflect reduced object churn and overall improved allocation patterns.
• No breaking changes:
  The public interfaces have not been changed. The change should not break any dependent library.

Benefits

• Lower Memory Footprint:
  Dramatically reduces allocations related to string operations, easing runtime memory pressure.
• Improved Performance:
  Faster evaluations due to fewer expensive object and string operations.
• Better Scalability:
  Enhanced library stability and efficiency under heavy or high-throughput usage.
• Targeted Exception Diagnostics:
  jsonPath remains available for error handling and diagnostics, but is computed only as needed.

[guidobrei]

@jamsesso, @magnarn this is a proposal to reduce the memory footprint of the evaluation again.

It effectively makes the jsonPath property introduced in #53 obsolete again. I did not remove it for backwards compatibility.
WDYT?

[magnarn]

I think this is awesome!

Thanks for fixing it. I wish I had though of this when introducing the json path.

[guidobrei]

I've added additional tests to cover malformed expressions.

[guidobrei]

@jamsesso any chance we could fix the issue soon?