Fix: ISE 500 when non-numerical value appears in range search in JSON column

[psrok1]

Your checklist for this pull request

• I've read the contributing guideline.
• I've tested my changes by building and running the project, and testing changed functionality (if applicable)
• I've added automated tests for my change (if applicable, optional)
• I've updated documentation to reflect my change (if applicable)

What is the current behaviour?

When we try to use non-numerical value in range search, query fails with Internal server error because of incorrectly formatted jsonpath.

What is the new behaviour?

When value doesn't look like a number or known JSON literal, value is properly quoted and escaped before put in the jsonpath query.

Test plan

Added automated test to fulfill use-case mentioned in related issue

Closing issues

closes #952