`charon alpha test mev` reads locks, builder_registration_overrides, and relays, and status reports which relays are healthy, and have the validator registered under the expected settings

🎯 Problem to be solved

We want it to be easier to check if a registration correctly updated. Right now you have to guess an api path on the relay side that we don't even know if all support, to check if your gas limit increased or your fee recipient address updated.

🛠️ Proposed solution

Put this status checking behind a charon test relay command. the command almost does similar things already, its still in alpha, we can use it as a pretty print of mev status imo (with something performance test-y too)

• Approved design doc: link
• Core team consensus on the proposed solution

Describe the solution to be implemented

🧪 Tests

• Tested by new automated unit/integration/smoke tests
• Manually tested on core team/canary/test clusters
• Manually tested on local compose simnet

Start with the existing charon alpha test mev command and its handling of locks, builder_registration_overrides, and relays. Clarify the approved design and core-team consensus for a charon test relay status check, including how healthy relays and validator settings are reported. Done means the behavior is agreed and covered by the automated and manual tests listed in the issue.