Loss of InvalidConfigurationException in favor of SerializationException in v7.7.1

[fdelsert-dkt]

Hi,

After upgrading to the latest version (7.7.1), we noticed that the previous InvalidConfigurationException has been replaced by a SerializationException containing a RestClientException.
This introduces a regression in my project in how schema compatibility issues are handled.

Previously, the KafkaAvroSerializer would throw an InvalidConfigurationException when encountering a critical configuration issue, such as schema incompatibility (409).
After the upgrade, the same scenario now throws a SerializationException, which wraps a RestClientException.

Our current workaround involves catching the SerializationException and inspecting the RestClientException for error code. However, this feels like a less elegant solution compared to the prior approach with InvalidConfigurationException.