ci(features): fix zepter feature propagations for the DogeOS components

The Reth 2 component migration left two feature propagations un-updated,
which zepter flags (the target base's zepter check is green):

- rollup-node-primitives `arbitrary` -> `dogeos-reth-primitives/arbitrary`
  (Cargo.lock gains the required `arbitrary` edge under
  `dogeos-reth-primitives`);
- scroll-network `serde` -> `dogeos-protocol-types/serde`.

`zepter run check` now passes. No default-feature behavior change.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: dghelm

Cargo.lock

@@ -51,6 +51,7 @@ serde = [
     "reth-storage-api/serde",
     "dogeos-hardforks/serde",
     "rollup-node-primitives/serde",
+    "dogeos-protocol-types/serde",
 ]
 test-utils = [
     "reth-chainspec/test-utils",

crates/network/Cargo.toml

@@ -61,6 +61,7 @@ arbitrary = [
     "dogeos-protocol-types/arbitrary",
     "alloy-eips/arbitrary",
     "dogeos-reth-primitives/std",
+    "dogeos-reth-primitives/arbitrary",
     "reth-primitives-traits/arbitrary",
     "alloy-consensus/arbitrary",
     "alloy-rpc-types-engine/arbitrary",