Backporting implementation of LogForwarder to 1.8

[rgildein]

Context

We need to backport changes related with usage of LogForwarder to provide logging relation also to Kubeflow 1.8.

This task is related with follogin issues:
canonical/argo-operators#173
canonical/dex-auth-operator#194
canonical/kfp-operators#488
canonical/kfp-operators#489
canonical/kfp-operators#490
canonical/kfp-operators#491
canonical/kfp-operators#492
canonical/kfp-operators#493
canonical/kfp-operators#494
canonical/kfp-operators#495
canonical/notebook-operators#370
canonical/notebook-operators#371
canonical/katib-operators#186
canonical/katib-operators#187
canonical/knative-operators#184
canonical/kubeflow-dashboard-operator#195
canonical/envoy-operator#104
canonical/katib-operators#188
canonical/admission-webhook-operator#133
canonical/kubeflow-volumes-operator#136
canonical/pvcviewer-operator#40
canonical/kubeflow-tensorboards-operator#110
canonical/kubeflow-tensorboards-operator#111
canonical/kserve-operators#236
canonical/kubeflow-profiles-operator#167
canonical/mlmd-operator#85
canonical/oidc-gatekeeper-operator#152
canonical/seldon-core-operator#253

What needs to get done

1. Backport logging implementation to KF 1.8

Definition of Done

1. All charms mention by issues above should be backported with logging relation
2. These should be tested.

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5993.

This message was autogenerated