Add a defensive check to class resolution during deserialization

[yannaingtun]

This change restricts class resolution in ClassLoaderObjectInputStream by validating deserialized classes against an expected base type, preventing unexpected classes from being loaded.

Addresses issue #280.

[hrj]

Thanks. Can you also modify the callers to use the new constructor?

[yannaingtun]

Hi @hrj, thanks for the feedback.
I’ve updated all callers to use the new constructor:

new ClassLoaderObjectInputStream(..., expectedClass)

For now, I used Serializable.class as the base type since all retrieved objects are expected to be Serializable. Please let me know if you'd prefer a more specific base type for any of the call sites.

PR is ready for another review.

[hrj]

Thanks, it looks like a good start. If you can make the retrieved class a bit more specific that will help tighten the bolts around this.

If you are not able to, I will try to chip in next week.

PS: When you are ready, you can sign the commit(s) in order to satisfy the DCO: https://wiki.linuxfoundation.org/dco