Queries: Support "notIn" with string arrays like "in" does

On queries, you can use string array "overloads" for in in the following ways:
QueryBuilder<T> in(Property<T> property, String[] values)
QueryBuilder<T> in(Property<T> property, String[] values, StringOrder order)

The same "overloads" are not supported for notIn though, which only supports int and long arrays

Edit: additional suggestions via #1129:

• Implement doesNotContain, doesNotEndWith, doesNotStartWith into Property or
• Create QueryCondition.not() that would allow to negate any given QueryCondition

Example use case for the latter :

Character_.lastName.equal("lannister", QueryBuilder.StringOrder.CASE_INSENSITIVE)
.and(Character_.firstName.startsWith("ty", QueryBuilder.StringOrder.CASE_INSENSITIVE)) // "Tywin", "Tyrion", "Tytos"

Character_.lastName.equal("lannister", QueryBuilder.StringOrder.CASE_INSENSITIVE)
.and(Character_.firstName.startsWith("ty", QueryBuilder.StringOrder.CASE_INSENSITIVE).not()) // "Cersei", "Jaime", "Lancel"

Commencez par les QueryBuilder et Property query APIs nommées dans l’issue, en comparant le string-array existant dans les surcharges de in avec les surcharges de notIn pour int-array et long-array. Suivez les tests de query associés, puis confirmez que string-array notIn prend en charge les mêmes formes de surcharge et le même comportement que in.