Running a validator client with a --<network> option differing than the one of the connected BN leads to strange results.

[nalepae]

Describe the bug

BN launch command:

bazel run //cmd/beacon-chain --config=release -- --execution-endpoint=http://localhost:8551 --holesky --jwt-secret <...> --checkpoint-sync-url https://holesky.beaconstate.info --genesis-beacon-api-url https://holesky.beaconstate.info --accept-terms-of-use --force-clear-db

Please note the --holesky.

VC launch command:

bazel run //cmd/validator -- --sepolia --wallet-password-file <...> --suggested-fee-recipient <...> --enable-beacon-rest-api

Please note:

• The --sepolia, which differs from the --holesky in BN
• The --enable-beacon-rest-api

In this case, at log level, everything runs perfectly: No error displayed neither on BN or VC side.
Particularly, on VC side, we get these logs:

 INFO client: Submitted new attestations blockRoot=0x21a3e4e7d95f committeeIndices=[10 22] pubkeys=[0x8df7346b379b 0x8b508ff750a3] slot=1360136 sourceEpoch=42503 sourceRoot=0xe8c006a2ecb7 targetEpoch=42504 targetRoot=0x695b543a4621

However, these attestations seem to never been included in any block.

In such a case, I would expect at least one error displayed on the VC side.

Additional information:
Running the VC without the --enable-beacon-rest-api flags, but still with the wrong --<network> flags seems to work correctly: No error displayed on neither on the BN nor on the VC, but this time attestations seems to be included. Please note I did not check for other validators duties.