Improve clickhouse-keeper manifests

[Slach]

Depends on ClickHouse/ClickHouse#53481

This will help a lot for maintainers to adopt your Pull Request.

Important items to consider before making a Pull Request

Please check items PR complies to:

• All commits in the PR are squashed. More info
• The PR is made into dedicated next-release branch, not into master branch¹. More info
• The PR is signed. More info

--

¹ If you feel your PR does not affect any Go-code or any testable functionality (for example, PR contains docs only or supplementary materials), PR can be made into master branch, but it has to be confirmed by project's maintainer.

[Slach]

Wait when resolve ClickHouse/ClickHouse#53481 and ClickHouse/ClickHouse#54129

[bputt-e]

does this fix the issue where force-recovery was always set to the first pod if I'm running a 3 clickkeeper cluster? It seems odd that force-recovery was always set to the first pod as if that pod were restarted or offline for a period of time, it effectively tells the rest of the clickkeeper instances that they must use the first pods state

[Slach]

@bputt-e
using --force-recovery in old manifest required for prefer XML configs more priority then internal NuRaft state which stored in /var/lib/clickhouse-keeper, without this option even when you change XML config <raft_configuration> it will have no effect

in the new approach, we are trying to use command reconfig, which also stay not fully operable