eth/catalyst: allow fcuV3 for BPO forks (ethereum#32615)

This fixes an issue with the engine API after BPO forks have passed.

Author: fjl

eth/catalyst/api.go

@@ -213,8 +213,8 @@ func (api *ConsensusAPI) ForkchoiceUpdatedV3(update engine.ForkchoiceStateV1, pa
 return engine.STATUS_INVALID, attributesErr("missing withdrawals")
 case params.BeaconRoot == nil:
 return engine.STATUS_INVALID, attributesErr("missing beacon root")
-case !api.checkFork(params.Timestamp, forks.Cancun, forks.Prague, forks.Osaka):
-return engine.STATUS_INVALID, unsupportedForkErr("fcuV3 must only be called for cancun or prague payloads")
+case !api.checkFork(params.Timestamp, forks.Cancun, forks.Prague, forks.Osaka, forks.BPO1, forks.BPO2, forks.BPO3, forks.BPO4, forks.BPO5):
+return engine.STATUS_INVALID, unsupportedForkErr("fcuV3 must only be called for cancun/prague/osaka payloads")
 }
 }
 // TODO(matt): the spec requires that fcu is applied when called on a valid