PathNotFoundException has no stack trace

[darrengreaves]

PR #775 has caused an issue.

PathNotFoundException was being used for flow control so was deliberately suppressing stack traces - the PR fixed that but should also have updated PathNotFoundException to no longer suppress stack traces.
The outcome of this is that errors now appear in the logs without any stack trace attached. 😫

[twhitmorenz]

Also observing this using JsonPath 2.7.0. Suppressing stacktraces is a bit of an unfortunate idea that ends up with rather engineering-hostile effects.

After all it doesn't just suppress trace of JsonPath internals, it suppresses the trace thru our application code it took to get there. On behalf of all engineers, please don't do this.

[jdimeo]

Apparently it was a big performance impact. I can understand that but it should be configurable, we're totally flying blind while we try to work out our logic.