feat: add protocol ID change to v1

Author: meyer9

docs/base-chain/specs/upgrades/azul/exec-engine.mdx

@@ -131,3 +131,9 @@ The Base-specific behavior is:
 Base-specific predeploys and other OP Stack system contracts documented in the
 [predeploys specification](../../protocol/execution/evm/predeploys) are not serialized into
 `eth_config` unless they are part of the EIP-7910 schema.
+
+## P2P Changes
+
+### Discovery protocol now uses `basev0` protcol ID
+
+The discovery protocol now uses `basev0` as the protocol ID. This allows Base nodes to find each other more quickly, especially on  networks with fewer nodes like Sepolia.

docs/base-chain/specs/upgrades/azul/overview.mdx

@@ -31,6 +31,7 @@ Only `base-consensus` and `base-reth-node` will support the Base Azul hardfork.
 - [EIP-7642: eth/69](/base-chain/specs/upgrades/azul/exec-engine#eth69)
 - [EIP-7910: eth_config RPC Method](/base-chain/specs/upgrades/azul/exec-engine#eth_config-rpc-method)
 - [Remove Account Balances & Receipts](/base-chain/specs/upgrades/azul/exec-engine#remove-account-balances--receipts)
+- [Use `basev0` protocol ID for discv5](/base-chain/specs/upgrades/azul/exec-engine#discovery-protocol-now-uses-basev0-protcol-id)
 
 ## Proofs