[FEATURE] Improve built-in secure transports support

[reta]

Is your feature request related to a problem? Please describe

In #12256, we have added built-in secure transports support into OpenSearch core, the further integration with transport plugins and security plugin revealed a couple of areas of improvements.

Describe the solution you'd like

• split SecureTransportSettingsProvider into SecureTransportSettingsProvider (native transport) and SecureHttpTransportSettingsProvider (HTTP transport): some transport plugins only provide one kind of transport, having fine grained control of the security settings only for particular transport would simplify the configuration
• support TransportAdapterProvider<?> abstraction to alter the transport specific processing pipelines: the use cases here are primarily driven by security plugin which adds header verifier and decompressor, since every transport has pretty much independent implementation, it becomes the responsibility of the SecureTransportSettingsProvider and SecureHttpTransportSettingsProvider providers to supply the right one for a particular transport

Related component

Other

Describe alternatives you've considered

N/A

Additional context

• [FEATURE] Built-in secure transports support #12256

[peternied]

[Triage - attendees 1 2 3 4 5 6 7]
@reta Thanks for filing this issue, looking forward to seeing these improvements.