Remote Signer: Electra

[james-prysm]

What type of PR is this?

Feature

What does this PR do? Why is it needed?

updates the remote signing to handle changes from PRs ethereum/remote-signing-api#15 and ethereum/remote-signing-api#17

Kurtosis testing with the following settings

participants:
  - el_type: geth
    el_image: ethpandaops/geth:prague-devnet-5-a193537
    cl_type: prysm
    cl_image: gcr.io/prysmaticlabs/prysm/beacon-chain:latest
    vc_type: prysm
    vc_image: gcr.io/prysmaticlabs/prysm/validator:latest
    use_separate_vc: true
    use_remote_signer: true
  - el_type: geth
    el_image: ethpandaops/geth:prague-devnet-5-a193537
    cl_type: prysm
    cl_image: gcr.io/prysmaticlabs/prysm/beacon-chain:latest
    vc_type: prysm
    vc_image: gcr.io/prysmaticlabs/prysm/validator:latest
    use_separate_vc: true
    use_remote_signer: true
network_params:
  electra_fork_epoch: 1
additional_services:
  - dora

Which issues(s) does this PR fix?

Fixes #

Other notes for review

Acknowledgements

• I have read CONTRIBUTING.md.
• I have made an appropriate entry to CHANGELOG.md.
• I have added a description to this PR with sufficient context for reviewers to understand this PR.

[prestonvanloon]

This pattern seems bad. Why not just add a label to mention the fork?

	blockSignRequestsTotal = promauto.NewCounter(prometheus.CounterOpts{
		Name: "remote_web3signer_block_sign_requests_total",
		Help: "Total number of block sign requests",
	})
	blindedBlockSignRequestsTotal = promauto.NewCounter(prometheus.CounterOpts{
		Name: "remote_web3signer_blinded_block_sign_requests_total",
		Help: "Total number of blinded block sign requests",
	})

Then use it with appropriate value

blockSignRequestsTotal.WithLabelValues("fork", "electra").Inc()

I think we should do this for the v6 release. There is no reason to report old fork metrics by registering a counter for every fork when we could use labels. Can you add this for Electra, then we can make the breaking change for old metrics in v6?