EPIC: Unify and extend HTTP Client Configuration Capabilities

[jakobmoellerdev]

Description

We want to be able to globally (and locally) configure HTTP Client specific settings such as

• PROXY Settings
• Certificate Settings
• Secure / Insecure Flags

as well as inject global handlers such as

• Logging Middleware
• Middleware for Tracing (down the line)

For this we need to establish a common configuration structure that can be used within OCM globally as well as be injected into accessmethods on demand later on (to locally override).

An example config might look like this:
https://gist.github.com/hilmarf/130eae7fad45e3602f1b061bbb6abf49#file-ocmconfig-L91-L106

[jakobmoellerdev]

Relates to #1118 as this would have been great there but we didnt have a big config struct yet.

[jakobmoellerdev]

#1064 is also related as its an initial take but as of writing still lacks the integration into the global config struct

[hilmarf]

sample .ocmconfig contains a proposal for a new config type: http.config.ocm.software