Inspect all the forced class casting in the repo

Currently we see a few type casting errors in a few places:
{code:java}
org.apache.hudi.common.table.timeline.versioning.v2.CommitMetadataSerDeV2.deserialize(CommitMetadataSerDeV2.java:88)
at org.apache.hudi.common.table.timeline.HoodieTimeline.readNonEmptyInstantContent(HoodieTimeline.java:153)
at org.apache.hudi.common.table.timeline.HoodieTimeline.readRollbackPlan(HoodieTimeline.java:244)
at org.apache.hudi.metadata.HoodieTableMetadataUtil.getRollbackedCommits(HoodieTableMetadataUtil.java:2034)
... 30 more
Caused by: java.lang.ClassCastException: class org.apache.avro.generic.GenericData$Record cannot be cast to class org.apache.avro.specific.SpecificRecordBase (org.apache.avro.generic.GenericData$Record and org.apache.avro.specific.SpecificRecordBase are in unnamed module of loader 'app'){code}

The reason is some JDK releases does now allow type coersion for instantces from different classloaders,
see issue https://github.com/apache/hudi/issues/13410 for more details.

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-9573
- Type: Improvement

Start by reading the reported failure at CommitMetadataSerDeV2.java:88 and the related context in HoodieTimeline.java:153 and :244. Compare the forced casts involved with the classloader coercion issue linked in the report; the issue does not specify a test or define what changes should be made, so clarify the expected outcome before starting implementation.

Written by the indexing model from the issue text.