Fix family mismatch crash in IpInetAddressMatcher

[minwoo-3]

Fixes #19733

IpInetAddressMatcher#matches(InetAddress) (backing IpAddressMatcher /
InetAddressMatchers, added in 7.1) compares the byte arrays of the
configured address and the address being checked without first verifying
they're the same length.

The class-level Javadoc on IpAddressMatcher documents:

a matcher which is configured with an IPv4 address will never match a
request which returns an IPv6 address, and vice-versa.

When the configured CIDR mask requires more full bytes than the shorter of
the two addresses has (e.g. an IPv6 /64 matcher checked against an IPv4
address), and the leading bytes happen to be equal up to the shorter
array's length, the comparison loop indexes past the end of the shorter
array and throws ArrayIndexOutOfBoundsException instead of returning
false as documented.

Repro (see #19733 for the full write-up):

IpAddressMatcher matcher = new IpAddressMatcher("2001:db8::/64");
matcher.matches("32.1.13.184"); // throws ArrayIndexOutOfBoundsException

This PR adds a length check that returns false immediately when the two
addresses are different lengths (different families), matching the
documented contract, plus two regression tests covering both directions
(IPv6-configured matcher checked against IPv4, and vice versa).

Ran ./gradlew format and :spring-security-core:check locally; both
pass, along with the full IpInetAddressMatcherTests suite.