Avoid calling BeaconState.clone() in beacon-node

[twoeths]

Problem description

The only place we modify our BeaconState is state-transition
so either move the concerning function there (rewards api is an example) or do not use it
the reason is we also should not call it when we integrate to lodestar-z

Solution description

Check all places calling BeaconState.clone() and either move to state-transition or not to call it

Additional context

part of #8650

[twoeths]

we should also not call commit() inside packages/beacon-node because we should not have any pending modifications ever
it's confusing to do that and causes a concern for the native BeaconStateView