Cardano Updates

Currently, the `B` constructor contains a `ByteString` (pinned in
memory) with a max length of 64 bytes. Since the `ByteString` is small
and can be instantiated frequently, it makes more sense to use an
unpinned byte array representation (`Data.Array.Byte.ByteArray`) so
that we can take advantage of Haskell's garbage collection to improve
memory allocation of objects in the heap.

We also place an upper bound on `nothunks` because of new orphan
instance (`instance NoThunks ByteArray`) that is going to be upstreamed.

We do should *not* provide a default implementation for 'fromPlutusData'
because types should always be invertible from 'PlutusData'. Therefore,
we force the user to make a conscious decision to not provide an
implementation for this function.

Currently, the `B` constructor contains a `ByteString` (pinned in
memory) with a max length of 64 bytes. Since the `ByteString` is small
and can be instantiated frequently, it makes more sense to use an
unpinned byte array representation (`Data.Array.Byte.ByteArray`) so
that we can take advantage of Haskell's garbage collection to improve
memory allocation of objects in the heap.

After removing distinct_bytes, the CDDL generator could produce
duplicate empty byte strings for plutus scripts in nonempty_set
collections (tag 258). The Set decoder would deduplicate them,
causing a length mismatch error. Fix by generating 32-byte random
bytestrings which makes collisions virtually impossible.

Also mark proposal_procedure antiCborSpec as pending due to
unrelated protver decoder issue.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

Refactor shelley BBODY transition to export reusable validations to
future eras and update the BBODY signal.

Move isOverlaySlot calculation into incrBlocks.

Add withGenerator to plutus_v4_script to prevent set collisions, matching
the fix for V1/V2/V3. Enable previously disabled Dijkstra tests that now
pass: AuxData roundtrip, TxOut/Script/TxWits ArbitraryValidate,
PParamsUpdate/ProposalProcedure/GovAction ArbitraryValidate, and TxAuxData
decoder equivalence. Update xdescribe reasons for tests that remain
disabled (plutus_v4_script tag 4 not yet supported by decoder, metadatum
validation, empty redeemers).

Co-Authored-By: Claude Opus 4.6 <[email protected]>

We do should *not* provide a default implementation for 'fromPlutusData'
because types should always be invertible from 'PlutusData'. Therefore,
we force the user to make a conscious decision to not provide an
implementation for this function.

Add `mkPlutusTxInfoFromResult` and `toPlutusTxInfoForPurpose` helpers to
aid in using this nested complexity.