Add ensureCustomSerialization to ensure that headers are serialized correctly with multiple transport hops

[cwperks]

Description

This PR fixes multiple issue:

• [BUG] Unexpected failure while sending request, -84 is not a valid id opensearch-project/security#4494
• [BUG] DLS Performance with 2.16 opensearch-project/security#4670

When upgrading from 2.11/2.12/2.13 to >= 2.14, there can be an issue when deserializing threadContext headers on the receiving node due to the transmitting node re-using the serialization format from a previous transport hop.

This was particular seen in scenarios where there are a chain of transport hops, such as 2.14 (Coordinator node) -> 2.14 node -> 2.12 node

These scenarios can happen on ingestion during rolling upgrades where a replica shard may temporarily be on an older node than a primary shard.

This PR adds logic in the SecurityInterceptor to re-serialize the headers if they have previously been populated from a prior transport hop for backwards compatibility.

This PR also removes logic ensureJdkSerialization.

• Category (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)

Bug fix

Issues Resolved

• [BUG] Unexpected failure while sending request, -84 is not a valid id opensearch-project/security#4494
• [BUG] DLS Performance with 2.16 opensearch-project/security#4670

Testing

Creating this PR in Draft until testing details are added.

Check List

• New functionality includes testing
• New functionality has been documented
• New Roles/Permissions have a corresponding security dashboards plugin PR
• API changes companion pull request created
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.