feat(log): log http requests for OCI and docker based on trace level by injecting a logger

[jakobmoellerdev]

What this PR does / why we need it

it is now possible to inject a trace attribute to OCMs logging architecture to allow tracing back HTTP calls for oci registries and the docker client:

ocm --logkeys /+ocm/oci=trace [YOUR COMMAND INTERACTING WITH OCI HERE]

Note that this does not take care of all access types yet because we dont have a unified http.Client.

Note that it is now also possible to pass /+ocm/docker=trace to enable logging for the docker client infrastructure, or set --loglevel=trace to get a full tracelog with HTTP statements.

Authorization Headers are redacted

Which issue(s) this PR fixes

This allows introspecting HTTP calls for debugging purposes, e.g.

bin/ocm --logkeys /+ocm/oci=trace transfer artifact CommonTransportFormat::XXX/ocm/gen/ctf//component-descriptors/ocm.software/ocmcli ghcr.io/jakobmoellerdev/ocm:latest
copying CommonTransportFormat::XXX/ocm/gen/ctf//component-descriptors/ocm.software/ocmcli:0.17.0-dev to ghcr.io/jakobmoellerdev/ocm:latest...
 2024-11-20T19:09:14+01:00 trace   [ocm/oci/ocireg] roundtrip header="{\"Accept\":[\"application/vnd.ocm.software.component.config.v1+json, */*\"],\"User-Agent\":[\"containerd/1.7.23+unknown\"]}" host=ghcr.io method=HEAD namespace=jakobmoellerdev/ocm url=https://ghcr.io/v2/jakobmoellerdev/ocm/blobs/sha256:0351859d79ce5900e610226ed03ab0fb5586f4f19b26693487bf13fac1ce6923
 2024-11-20T19:09:14+01:00 trace   [ocm/oci/ocireg] "query credentials" host=ghcr.io namespace=jakobmoellerdev/ocm pass="***" user=jakobmoellerdev

[fabianburth]

Looks good