Updating the key in a non deployable pipelines leads to broken fluent-bit config

Description

When a secret is updated, then this change should be updated in the fluentbit config only if we the logpipeline using this is deployable.

Currently when there is an update to the secret we update the secret for all the pipelines but the sections configmap is updated only for the deployable pipelines. This causes following error in telemetry operator

{"level":"INFO","timestamp":"2023-10-24T06:20:42Z","caller":"secretref/secret_ref.go:61","message":"Unable to find key 'host' in secret 'mockserver-host'","context":{"controller":"logpipeline","controllerGroup":"telemetry.kyma-project.io","controllerKind":"LogPipeline","LogPipeline":{"name":"logpipeline-http-sample"},"namespace":"","name":"logpipeline-http-sample","reconcileID":"e1afc8f6-9a04-4948-854c-904beb756be3"}}

and following error in fluent-bit

[2023/10/20 07:15:31] [ warn] [read_glob] glob: [/fluent-bit/etc//dynamic/*.conf] no match
[2023/10/20 07:15:31] [error] configuration file contains errors, aborting.

The current behaviour causes broken fluent-bit config and fluent-bit does not start.

Expected result

When a secret is updated then only deployable pipelines should be reconciled.

Actual result

Steps to reproduce

Create a log pipeline that uses secret
Change the secret key from host to host1

kyma-project / telemetry-manager

Updating the key in a non deployable pipelines leads to broken fluent-bit config #485