Make kiwi's validation annotations in kiwi usable in collections

[sleberknight]

For examples, see this article: https://www.baeldung.com/bean-validation-container-elements (and of course the first google result was on Baeldung)

It lets you do this:

@Data
class Customer {

    @NotBlank
    private String name;

    @NotEmpty
    private List<@NotBlank String> emailAddresses;
}

In the above emailAddresses can't be empty (or null), and each list element must not be blank.

See @NotBlank or any of the standard Java Beans Validation annotations that support this.

Assuming we want to to do this, we should probably break it up into one task per annotation for smaller commits.

[sleberknight]

This "just works", for example suppose we have the following contrived class:

@Value
static class HolderOfNumbers {
    @NotBlank
    String name;

    List<@IntValue String> numberList;
    Set<@IntValue String> numberSet;
    Map<@IntValue String, @IntValue String> numberMap;
}

This class uses kiwi's @IntValue annotation to validate that a CharSequence contains a value that can be converted to an int or Integer, and @LongValue which is similar except long instead of int.

Then suppose we have a HolderOfNumbers instance:

var holder = new HolderOfNumbers(
    "",
    List.of("foo", "bar", "baz"),
    Sets.newLinkedHashSet(null, "goo"),
    KiwiMaps.newLinkedHashMap(
        null, "val1",
        "2", "42",
        "3", "63",
        "4", "oops",
        "badkey", "105",
        "blue", "green"
    )
);

We can validate it and print the results:

var violations = KiwiValidations.validate(holder);

for (var violation : violations) {
    var propertyName = violation.getPropertyPath().toString();
    var invalidValue = violation.getInvalidValue();
    var message = violation.getMessage();
    System.out.printf("%s with invalid value '%s' %s%n", propertyName, invalidValue, message);
}

The results are:

numberList[2].<list element> with invalid value 'baz' must be convertible to an integer
numberMap<K>[blue].<map key> with invalid value 'blue' must be convertible to an integer
numberMap[].<map value> with invalid value 'val1' must be convertible to a long
numberList[1].<list element> with invalid value 'bar' must be convertible to an integer
numberMap[4].<map value> with invalid value 'oops' must be convertible to a long
numberMap<K>[].<map key> with invalid value 'null' must be convertible to an integer
numberSet[].<iterable element> with invalid value 'null' must be convertible to a long
numberMap[blue].<map value> with invalid value 'green' must be convertible to a long
numberSet[].<iterable element> with invalid value 'goo' must be convertible to a long
numberList[0].<list element> with invalid value 'foo' must be convertible to an integer
numberMap<K>[badkey].<map key> with invalid value 'badkey' must be convertible to an integer
name with invalid value '' must not be blank

So, there is actually nothing to do here, since Jakarta Bean Validation 3.x works out of the box. And this was actually introduced in Beans Vaidation 2.0, so it has worked for a while!