Avoid chainid underflow when v = 0

[pcw109550]

This PR fixes error encountered during executing erigon snapshot based on op goerli database:

./erigon snapshots retire --datadir=op-erigon-datadir

Error:

parse transaction: invalid chainID, 18446744073709551598 (expected 420), block: 1" stack="[main.go:33 panic.go:884 snapshots_cmd.go:448 command.go:274 command.go:267 command.go:267 app.go:332 app.go:309 main.go:38 proc.go:250 asm_arm64.s:1172]"

Lets hexify 18446744073709551598 == 0xffffffffffffffee. This specific number was observed when v = 0 and try to derive chainID from v. Similar issue: testinprod-io/op-erigon#14.

v = 0 case only occur in optimism prebedrock state, and these edge case must be error handled. If v = 0, do not derive and use config's chainID. Also, store v = 0 for initializing vByte.