feat: seamlessly retry requests on backend failure for the Elasticsearch filter

[medcl]

What does this PR do

Previously, when one of the nodes was down, any requests sent to that node— including read requests—would fail. Recovery would only occur after the node received enough failure tickets or reached the refresh interval, which could take significant time. This delay often led to numerous failed requests, even when backup nodes were available to handle them.

With this change, requests are seamlessly retried with other nodes by default, minimizing interruptions and improving reliability.

Rationale for this change

Standards checklist

• The PR title is descriptive
• The commit messages are semantic
• Necessary tests are added
• Updated the release notes
• Necessary documents have been added if this is a new feature
• Performance tests checked, no obvious performance degradation