Issue with new geth-op and geth-node upgrade

**Describe the bug**
Node could not sync due to to old version with deadline Thu Jan 11 17:00:01 UTC 2024 (unix timestamp: 1704992401)
I upgraded op-node (op-node v1.4.0) and op-geth (v1.101304.2)

Add flags for op-node : --network=op-mainnet and op-geth: --op-network=op-mainnet

The issue with sync
`no peers ready to handle block requests for more P2P requests for L2 block history target=114,696,812 end=ad8ba5..6b8c56:114703049 current=114,702,845`

**Getting in the log**

`
INFO [01-11|21:30:47.516] Advancing bq origin origin=1a4d5e..2bf44e:18985035 originBehind=false
INFO [01-11|21:30:47.999] Optimistically queueing unsafe L2 execution payload id=0b6659..f0e187:114703076
WARN [01-11|21:30:47.999] Could not add unsafe payload id=0b6659..f0e187:114703076 timestamp=1,705,004,929 err="cannot add duplicate payload 0x0b665981dafac6b2333f229cd605f9cccc14a04599d28a2e225c5ae6e2f0e187:114703076"
INFO [01-11|21:30:48.139] Advancing bq origin origin=bcf8e3..c55968:18985036 originBehind=false
INFO [01-11|21:30:48.139] created new channel origin=bcf8e3..c55968:18985036 channel=a4baf8..cb386d length=115,237 frame_number=0 is_last=true
INFO [01-11|21:30:48.139] Reading channel channel=a4baf8..cb386d frames=1
INFO [01-11|21:30:48.139] Optimistically queueing unsafe L2 execution payload id=094aa4..36e9e7:114703075
WARN [01-11|21:30:48.139] Could not add unsafe payload id=094aa4..36e9e7:114703075 timestamp=1,705,004,927 err="cannot add duplicate payload 0x094aa41435fce0248848b5001086281f14c0e91ad3ff0c49d1337eb2e636e9e7:114703075"
INFO [01-11|21:30:48.139] Optimistically queueing unsafe L2 execution payload id=23a2aa..eb7e24:114703074
INFO [01-11|21:30:48.407] attempting connection peer=16Uiu2HAmP8nPwENMbsgC7dgv5EmQXKsvbYy5vPjRxBLtpeBdww7x
INFO [01-11|21:30:48.802] Advancing bq origin origin=573c31..020b5e:18985037 originBehind=false
INFO [01-11|21:30:49.297] no peers ready to handle block requests for more P2P requests for L2 block history target=114,696,812 end=23a2aa..eb7e24:114703074 current=114,702,846
INFO [01-11|21:30:49.419] Advancing bq origin origin=8d0354..d00f8a:18985038 originBehind=false
WARN [01-11|21:30:49.763] failed p2p sync request peer=16Uiu2HAm1hmjDZjF27FP1oCQBS8ND9DWXZX1yyRNexTyr7eC5WL3 num=114,702,978 err="failed to open stream: failed to negotiate protocol: protocols not supported: [/opstack/req/payload_by_number/10/0]"
WARN [01-11|21:30:49.906] failed p2p sync request peer=16Uiu2HAmNuBC9F56kbHqg6cQj8jbSaRxC47rCd5PYaGhegDg233L num=114,702,975 err="failed to open stream: failed to negotiate protocol: protocols not supported: [/opstack/req/payload_by_number/10/0]"
INFO [01-11|21:30:49.949] Advancing bq origin origin=6a076e..7e8bdb:18985039 originBehind=false
INFO [01-11|21:30:50.468] Advancing bq origin origin=d6f053..66ce57:18985040 originBehind=false
INFO [01-11|21:30:51.086] Advancing bq origin origin=2565a4..899e71:18985041 originBehind=false
INFO [01-11|21:30:51.644] Advancing bq origin origin=28e906..6414ee:18985042 originBehind=false
WARN [01-11|21:30:51.644] tx in inbox with unauthorized submitter origin=28e906..6414ee:18985042 index=166 txHash=6f1176..799430 err=nil
INFO [01-11|21:30:52.243] Advancing bq origin origin=c3b336..178def:18985043 originBehind=false
INFO [01-11|21:30:52.733] no peers ready to handle block requests for more P2P requests for L2 block history target=114,696,812 end=23a2aa..eb7e24:114703074 current=114,702,846
INFO [01-11|21:30:52.849] Advancing bq origin origin=6171a9..f98789:18985044 originBehind=false
INFO [01-11|21:30:52.850] created new channel origin=6171a9..f98789:18985044 channel=a44b20..674004 length=116,023 frame_number=0 is_last=true
INFO [01-11|21:30:52.850] Reading channel channel=a44b20..674004 frames=1
INFO [01-11|21:30:53.443] Advancing bq origin origin=b45803..1ab2e5:18985045 originBehind=false
WARN [01-11|21:30:53.761] failed p2p sync request peer=16Uiu2HAm1hmjDZjF27FP1oCQBS8ND9DWXZX1yyRNexTyr7eC5WL3 num=114,702,862 err="failed to open stream: failed to negotiate protocol: protocols not supported: [/opstack/req/payload_by_number/10/0]"
WARN [01-11|21:30:53.906] failed p2p sync request peer=16Uiu2HAmNuBC9F56kbHqg6cQj8jbSaRxC47rCd5PYaGhegDg233L num=114,702,861 err="failed to open stream: failed to negotiate protocol: protocols not supported: [/opstack/req/payload_by_number/10/0]"
INFO [01-11|21:30:54.049] Advancing bq origin origin=007ab1..c0763f:18985046 originBehind=false
INFO [01-11|21:30:54.599] Advancing bq origin origin=66ddee..eab990:18985047 originBehind=false
INFO [01-11|21:30:55.259] Advancing bq origin origin=cc171a..ef0711:18985048 originBehind=false
INFO [01-11|21:30:55.999] Advancing bq origin origin=b8ccac..c96942:18985049 originBehind=false
`

**To Reproduce**
op-node (op-node v1.4.0) and op-geth (v1.101304.2)

**Expected behavior**
Node is synced after the upgrade

Start by reproducing the sync failure with op-node v1.4.0 and op-geth v1.101304.2, using the reported P2P negotiation and duplicate-payload log messages as entry points. Trace the L2 block-history request path and protocol negotiation; done means the upgraded node completes synchronization without these failures.

Written by the indexing model from the issue text.