fix: loki can not recovery after node restart

[heng4fun]

When the backend and read/write are restarted simultaneously or during recovery from a failure, the Loki cluster may continuously read but not be able to write or read.

related issue: https://github.com/apecloud/apecloud/issues/14705

[apecloud-bot]

/cherry-pick release-0.9

[apecloud-bot]

/cherry-pick release-1.0

[apecloud-bot]

🤖 says: Error cherry-picking.

Auto-merging addons/loki/templates/_helpers.tpl
CONFLICT (content): Merge conflict in addons/loki/templates/_helpers.tpl
Auto-merging addons/loki/templates/cmpd-read.yaml
CONFLICT (content): Merge conflict in addons/loki/templates/cmpd-read.yaml
Auto-merging addons/loki/templates/cmpd-write.yaml
CONFLICT (content): Merge conflict in addons/loki/templates/cmpd-write.yaml
Auto-merging addons/loki/templates/cmpv.yaml
Auto-merging addons/loki/values.yaml
error: could not apply 2c8f5a5... fix: loki can not recovery after node restart (#2267)
hint: After resolving the conflicts, mark them with
hint: "git add/rm ", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

[apecloud-bot]

🤖 says: ‼️ cherry pick action failed.
See: https://github.com/apecloud/kubeblocks-addons/actions/runs/19656409396

[apecloud-bot]

🤖 says: cherry pick action finished successfully 🎉!
See: https://github.com/apecloud/kubeblocks-addons/actions/runs/19656410099