feat: LogPipeline HTTP output mTLS support

[dennis-ge]

Description

Changes proposed in this pull request:

• mTLS support for LogPipeline HTTP output

Related Issues and Documents

Closes: #366

Traceability

• The PR is linked to a GitHub Issue.
• New features have a milestone label set.
• New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
• The corresponding GitHub Issue has a respective area label.
• The follow-up issues (if any) are linked in the Related Issues section.

Testability

The feature is unit-tested:

• Yes.
• No, because unit tests are not needed.
• No, because of ...

The feature is e2e-tested:

• Yes.
• No, because e2e-tests are not needed.
• No, because of ...

Tests conducted for the PR:

Codebase

• My code follows the Effective Go style guidelines.
• The code was planned and designed following the defined architecture and the separation of concerns.
• The code has sufficient comments, particularly for all hard-to-understand areas.
• This PR adds value and shows no feature creep.
• I have augmented the test suite that proves my fix is effective or that my feature works.
• Adjusted the documentation if the change is user-facing.

[a-thaler]

Can you please add a section to the docu https://kyma-project.io/#/telemetry-manager/user/02-logs?id=step-4-add-authentication-details-from-secrets, maybe just another block showing how to do it with client certs, similar as in https://github.com/kyma-project/telemetry-manager/blob/main/docs/user/03-traces.md#step-3b-add-authentication-details-from-secrets

I can see that the traces docu is not getting rendered well on the homepage, maybe you can fix that as well.

[NHingerl]

Excellent idea to make the code samples expandable, much better reading experience!

[chrkl]

/retest

[dennis-ge]

/retest

[shorim]

/test pull-telemetry-manager-unit-test

[shorim]

/retest

[a-thaler]

/retest