Core: Fix StructLikeWrapper.equals exception with comparator failure

[ebyhr]

StructLikeWrapper.equals threw an exception when the comparator threw an exception. This PR wraps the comparator.compare call in a try-catch so that type mismatches return false instead of propagating the exception.

The newly added test fails if we revert the StructLikeWrapper.equals change:

Wrong class, expected java.lang.Integer, but was java.lang.String, for object: test
java.lang.IllegalArgumentException: Wrong class, expected java.lang.Integer, but was java.lang.String, for object: test
	at org.apache.iceberg.PartitionData.get(PartitionData.java:126)
	at org.apache.iceberg.types.Comparators$StructLikeComparator.compare(Comparators.java:122)
	at org.apache.iceberg.types.Comparators$StructLikeComparator.compare(Comparators.java:95)
	at org.apache.iceberg.util.StructLikeWrapper.equals(StructLikeWrapper.java:91)
	at org.assertj.core.internal.StandardComparisonStrategy.areEqual(StandardComparisonStrategy.java:111)
	at org.assertj.core.internal.Objects.areEqual(Objects.java:231)
	at org.assertj.core.internal.Objects.assertNotEqual(Objects.java:227)
	at org.assertj.core.api.AbstractAssert.isNotEqualTo(AbstractAssert.java:394)
	at org.apache.iceberg.util.TestStructLikeWrapper.equalsTypeAndDataMismatch(TestStructLikeWrapper.java:45)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)

[anoopj]

Throwable is a bit too broad, Can you just catch the correct exception (which is IllegalArgumentException?) At worst, catch only Exception

[singhpk234]

+1, worst case we can just have RTE catched

[ebyhr]

I'm wondering if catching only IllegalArgumentException is really the right approach. Because the error originates from StructLike#get, the behavior depends on each implementation and the specific exception type is not guaranteed. I've changed this to catch RuntimeException instead.

[huaxingao]

Thanks @ebyhr for the PR! Thanks @anoopj @krvikash @nastra @singhpk234 for the review!