scripting benchmarks using find string

[wsargent]

Something is causing findString to be slow when used through the scripting language:

Benchmark                                      Mode  Cnt     Score     Error  Units
ScriptingBenchmarks.testFileConditionFail      avgt    5  4379.959 ± 579.831  ns/op
ScriptingBenchmarks.testFileConditionMatch     avgt    5  4610.075 ± 147.281  ns/op
ScriptingBenchmarks.testStringConditionFail    avgt    5  4649.784 ±  87.629  ns/op
ScriptingBenchmarks.testStringConditionMatch   avgt    5  4262.437 ± 191.742  ns/op
ScriptingBenchmarks.testWatchedConditionFail   avgt    5  5242.896 ±  93.665  ns/op
ScriptingBenchmarks.testWatchedConditionMatch  avgt    5  4700.055 ±  87.745  ns/op

Running the findString directly gives much better benchmarks, around 480 ns or so...

JsonPathBenchmarks.testPathConditionFail          avgt    5  474.741 ± 25.194  ns/op
JsonPathBenchmarks.testPathConditionPass          avgt    5  480.219 ± 93.595  ns/op
JsonPathBenchmarks.testStreamConditionFail        avgt    5   65.068 ±  6.154  ns/op
JsonPathBenchmarks.testStreamConditionPass        avgt    5   70.406 ±  1.922  ns/op