fix: validate json array order if strict mode

[novarx]

See #1157
A follow up to #1102
It seems that not validating the order of json arrays if strict is not the desired behaviour.

see #1102 (comment)

[novarx]

@bbortt

[etieskrill]

I think there is the need to configure the json array ordering separately from the strict mode. This should be configurable on a per-test basis. Probably by adding a new field to org.citrusframework.validation.json.JsonMessageValidationContext, something like checkArrayOrder, and choosing the validation method for array items based off of the new property, instead of strict. If the property was not set explicitly, the default should be false if non-strict, and true if strict, i think.

[tschlat]

lgtm

To have this properly documented, I kindly ask to create an issue to document the change, that non strict json validation now allows additional elements at any position in the array, while still enforcing the correct order of the control array elements.

[bbortt]

I'm fine with the current solution, knowing that @etieskrill is working on another feature to make this even more customizable.