interop: Handle first L1 Parent Ref in CandidateCrossSafe

[axelKingsley]

Extends: https://github.com/ethereum-optimism/optimism/pull/12818/files

The prior commit made it so that getting PreviousDerivedFrom would fail when there wasn't data behind the query. This should solve instances where the code attempts to attach 0-value parents to the L1 in WithParent.

However! The CanddiateCrossSafe function will manually use a zero-value ID to build parents into the L1 when the database is empty. This totally side-steps the returned error in the prior PR.

Infrastructure on L1 is failing with this line called out:

goroutine 140 [running]:
github.com/ethereum-optimism/optimism/op-supervisor/supervisor/types.BlockSeal.WithParent({{0x4d, 0x0, 0xfd, 0x89, 0x12, 0x1d, 0x13, 0xac, 0xff, 0x9a, ...}, ...}, ...)
    /app/op-supervisor/supervisor/types/types.go:247 +0x12e
github.com/ethereum-optimism/optimism/op-supervisor/supervisor/backend/db.(*ChainsDB).CandidateCrossSafe(0xc000320c60, {0xaf1139, 0x0, 0x0, 0x0})
    /app/op-supervisor/supervisor/backend/db/query.go:242 +0x459
github.com/ethereum-optimism/optimism/op-supervisor/supervisor/backend/cr

[jelias2]

Axel explained the logs from the panic and how it affects, lgtm