feat: add DERIVATION_VERSION_1 protocol constant

[patnir]

wire up alt-DA derivation version constant for privacy L3 dual-write:

Summary

• Add DERIVATION_VERSION_1 (0x01) next to existing DERIVATION_VERSION_0 (0x00) in base-protocol

Context: what is derivation version?

L2 nodes derive history by reading batcher txs on L1. Each batch-related L1 tx starts with a 1-byte tag so the node knows how to interpret the rest of the calldata:

Byte	Constant	Meaning
0x00	DERIVATION_VERSION_0	Inline data. Payload is the batch (compressed frames). Nodes parse it directly. This is today's calldata path.
0x01	DERIVATION_VERSION_1	Alt-DA pointer. Payload is a 34-byte commitment, not batch data. Nodes fetch the real bytes (0x00 ++ frames) from the DA server (S3).

Dual-write (PRIV-1972) posts both per batch: a v0 calldata tx (primary, nodes use today) and a v1 commitment tx (shadow, points to the same bytes in S3). This PR only names the v1 byte; the batcher and derivation resolver wire it up in follow-on PRs.

Test plan

• cargo check -p base-protocol

type=routine
risk=low
impact=sev5

[linear]

PRIV-1972

[github-actions]

❌ base-std fork tests did not run

The build or setup step failed before any tests could execute. Check the workflow logs for details.

[robriks]

LGTM !