Marks collector_fees in snapshot as unused

[brooksprumo]

Problem

The collector_fees field is unused by Bank, and thus the snapshot.

Summary of Changes

Remove it from the bank, and mark as unused in the snapshot.

[brooksprumo]

Frozen abi digest changed due to renaming the field.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.0%. Comparing base (8f1d12f) to head (e791e5d).
⚠️ Report is 12 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #10851     +/-   ##
=========================================
- Coverage    83.0%    83.0%   -0.1%     
=========================================
  Files         836      836             
  Lines      316338   316327     -11     
=========================================
- Hits       262665   262625     -40     
- Misses      53673    53702     +29     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[brooksprumo]

There are zero writers to this field in the repo. And since it is private, it would require a helper fn to write to it. There isn't a helper fn that exposes the field in a way that would allow writing.

[brooksprumo]

"This field stopped being used with the activation of this: #583"

[brooksprumo]

@apfitzge - requesting your review since you reviewed #4773, which added the collector_fees log.

@steviez - requesting your review as someone that may know more about this field.

[apfitzge]

LGTM

[steviez]

Always good to drop dead stuff, snapshots looks correct as well in that we'll just populate a 0 to avoid breaking serde

[brooksprumo]

lol auto-merge merged before the windows CI checks completed?

[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.