.validate method using JSON path will accept any invalid expected value

**Citrus Version**
2.7.2

**Expected behavior**
expected to fail when expected value is set to any junk/random value when using a valid JSON path

**Actual behavior**
passes no matter what the expected value is set as

**Test case sample**
> Please, share the test case (as small as possible) which shows the issue
response body:
[
{
"key": 111,
"apuSerial": "NGE",
"fullApuSerial": "BENSAPUCHANGE",
"manufacturerCode": "123",
"oemPartNum": "123",
"tail": "tail",
"comment": "123",
"tags": "123",
"user": "ben",
"createTimeStamp": "2020-09-25T10:08:32.9433333-04:00",
"updateTimeStamp": "2020-09-25T10:11:23.042-04:00"
}
]

testPostJson(endpoint, searchBody).validate("$[:1].apuSerial", "chicken")

have tried json path as $..apuSerial as well, both tested to be valid using Insomnia

have also upped citrus version number to see if fixed in later releases

used testPostJson method:

protected HttpClientResponseActionBuilder testPostJson(String path, ClassPathResource payload){
basePostRequestBuilder(path)
.payload(payload);
return http()
.client(httpClient)
.receive()
.response(HttpStatus.OK)
.messageType(MessageType.JSON);
}

Start with the JSON-path validation used by .validate and reproduce the report through testPostJson using the supplied response body and path "$[:1].apuSerial". The work is done when an invalid expected value such as "chicken" fails validation while a matching value succeeds.

Written by the indexing model from the issue text.