Initiate different BeaconStateViews at cli

[twoeths]

Problem description

We should be able to decide to use a regular BeaconStateView (the current view of a typescript CachedBeaconStateAllForks) vs a NativeBeaconStateView at cli

Solution description

• Implement a NativeBeaconStateView (see Decouple beacon-node and state-transition #8650 for the interface). This contains a pointer to a zig BeaconState so that we can lazy load some fields, or run state-transition from there
• implement a feature flag to initiate NativeBeaconStateView vs a regular BeaconStateView
• pass the initiated BeaconStateView to BeaconNode
• part of the job is to sync pubkeys based on validator bytes so that we don't have to count on the current CachedBeaconStateAllForks

Additional context

No response

[twoeths]

closed via #9067