[release-1.26] Fix s3 snapshot restore

[brandond]

Proposed Changes

Don't try to read token hash and cluster id during cluster-reset

These fields are only necessary when saving snapshots to S3, and will block restoration if attempted

Types of Changes

bugfix

Verification

See linked issue

Testing

Linked Issues

• [Release-1.26] - Cluster Restore for s3 snapshot fails #8731

User-Facing Change

Further Comments

[codecov]

Codecov Report

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

Comparison is base (10379aa) 17.48% compared to head (67037f4) 17.47%.

Additional details and impacted files

@@               Coverage Diff                @@
##           release-1.26    #8734      +/-   ##
================================================
- Coverage         17.48%   17.47%   -0.02%     
================================================
  Files                94       94              
  Lines              6313     6319       +6     
================================================
  Hits               1104     1104              
- Misses             4976     4982       +6     
  Partials            233      233              

Flag	Coverage Δ
unittests	17.47% <0.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
pkg/etcd/etcd.go	24.40% <0.00%> (ø)
pkg/etcd/s3.go	0.00% <0.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.