Allow old Compounding Staking Strategy SSV validators to be removed

[naddison36]

Summary

Allows the 10 exited validators in the old CompoundingStakingSSVStrategy SSV cluster to be removed via the new ConsolidationController, then splits the old strategy cleanup into a follow-up governance proposal.

This avoids requiring the old SSV cluster to be empty before deploy script 196 executes.

Changes

• Updates ConsolidationController so removeSsvValidator(...) can forward removals for:
  • Native staking strategy 2
  • Old CompoundingStakingSSVStrategy
• Passes the old CompoundingStakingSSVStrategy into the ConsolidationController constructor.
• Updates the compounding validator removal task with --consol support so removals can go through ConsolidationController.
• Updates deploy script 196 to only deploy/upgrade/set registrators and set the new default compounding strategy.
• Adds deploy script 197 to withdraw remaining ETH from the old compounding SSV cluster and remove the old strategy from the OETH vault.
• Adds SSV cluster normalization so migrated ETH clusters use ethBalance as the cluster balance.

Operational Flow

1. Execute governance proposal 196.
2. Remove the 10 old compounding SSV validators via the controller:

   npx hardhat removeValidator \
     --network mainnet \
     --type new \
     --consol true \
     --operatorids 2070,2071,2072,2073 \
     --pubkey <PUBKEY>

3. Confirm the SSV cluster has validatorCount == 0.
4. Execute governance proposal 197 to withdraw remaining cluster ETH and remove CompoundingStakingSSVStrategyProxy from the OETH vault.

## Deploy Details

Script 196 now includes only the controller/strategy setup actions. It no longer withdraws from the old SSV cluster or removes the old strategy.

Script 197 is strict and refuses to proceed unless the old compounding SSV cluster has zero validators. On fork only, it simulates removing the 10 validators so the cleanup proposal can be tested end-to-end.

## Code Change Checklist

To be completed before internal review begins:

- [ ]  The contract code is complete
- [ ]  Executable deployment file
- [ ]  Fork tests that test after the deployment file runs
- [ ]  Unit tests *if needed
- [ ]  The owner has done a [full checklist review](https://github.com/OriginProtocol/security/blob/master/templates/Contract-Code-Review.md) of the code + tests

Internal review:

- [ ] Two approvals by internal reviewers


## Deploy checklist

Two reviewers complete the following checklist:

• All deployed contracts are listed in the deploy PR's description
• Deployed contract's verified code (and all dependencies) match the code in master
• Contract constructors have correct arguments
• The transactions that interacted with the newly deployed contract match the deploy script.
• Governance proposal matches the deploy script
• Smoke tests pass after fork test execution of the governance proposal

[codecov]

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 51.25%. Comparing base (94a41fb) to head (2668803).

Files with missing lines	Patch %	Lines
...rategies/NativeStaking/ConsolidationController.sol	75.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@                    Coverage Diff                    @@
##           nicka/vanilla-staking    #2914      +/-   ##
=========================================================
+ Coverage                  50.95%   51.25%   +0.29%     
=========================================================
  Files                        110      110              
  Lines                       4914     4917       +3     
  Branches                    1358     1361       +3     
=========================================================
+ Hits                        2504     2520      +16     
+ Misses                      2406     2392      -14     
- Partials                       4        5       +1     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sparrowDom]

nit: we would normally do any fork specific setup in the fixtures with the purpose of keeping the deploy files as clean as possible