validator: ignore too old tower error

[diman-io]

Problem

If the identity is changed on the validator using set-identity and there is a tower file for new identity, but the data in the file is outdated, then the validator terminates its operation.

Summary of Changes

Instead of terminating, the data for the tower will be taken from the current state of the cluster.

[codecov]

Codecov Report

Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (86b5f3c) 81.6% compared to head (c9f95dd) 81.6%.
Report is 4 commits behind head on master.

❗ Current head c9f95dd differs from pull request most recent head 8bff83a. Consider uploading reports for the commit 8bff83a to get more accurate results

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #35229     +/-   ##
=========================================
- Coverage    81.6%    81.6%   -0.1%     
=========================================
  Files         834      833      -1     
  Lines      224827   224836      +9     
=========================================
- Hits       183517   183500     -17     
- Misses      41310    41336     +26     

[AshwinSekar]

thanks for the change, if you could rebase and fix the conflict i'm happy to merge it. #35173 just landed which is why there's a conflict.

[diman-io]

thanks for the change, if you could rebase and fix the conflict i'm happy to merge it. #35173 just landed which is why there's a conflict.

@AshwinSekar Done

[diman-io]

I assume you will add v1.17 and v1.18

[AshwinSekar]

to fix the build warnings

[diman-io]

Ohh, my bad. It was 1 a.m. here, copy-paste is evil. I checked build, but not clippy.

[steviez]

Looks good to me!

[mergify]

Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule.

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.