Lodestar v2.0 Checklist

Supersedes #7011

The Lodestar team is planning a significant strategic shift in their development approach, moving towards using the Zig programming language and Bun JavaScript runtime to improve performance and ensure the client remains on Ethereum's critical path

Key motivations for this transition include:
- Performance improvements and memory efficiency through native libraries
- Better positioning on Ethereum's critical path and roadmap
- Understanding that our biggest contributions to Ethereum is performant infrastructure supporting mainnet rather than browser tooling
- Realizing that TypeScript has its limitations with runtimes that have deep, unpredictable performance quirks

This issue is to track milestones that will lead us to our first Lodestar v2.0 release. This release will compile goals alongside any breaking changes we'd like to make for usage.

## Issues/PRs
### Lodestar
- https://github.com/ChainSafe/lodestar/issues/7280 // https://github.com/ChainSafe/lodestar/pull/7867
- https://github.com/ChainSafe/lodestar/pull/7901
- https://github.com/ChainSafe/lodestar/issues/7183
- https://github.com/ChainSafe/lodestar/issues/5963
- https://github.com/ChainSafe/lodestar/issues/7777
- https://github.com/ChainSafe/lodestar/pull/7810
- https://github.com/ChainSafe/lodestar/issues/7753

## Other Tasks
- TODO: List deprecated CLI flags and removing them
- State diff: Add any other issues/PRs related to moving database repositories due to `StateArchiveRepository`
- Proposer boost: Add any other issues/PRs related to proposer boost enabled by default
- Backfill: Serve blocks up to `MIN_EPOCHS_FOR_BLOCK_REQUESTS` (and blobs) after checkpoint syncing the node to last finalized