Cardano Updates

- mapNoMatchingKey: map leftover with no matching key (generic message)
- listZeroOrMore: list with zero-or-more rule and leftover elements
- mapNestedValue: map with nested value that partially matches

Show the closest matching postponed rule when leftover key-value pairs
remain after all rules have been tried. The exhausted rules are
re-evaluated against the first leftover KV pair, and the best match
(key matched, value failed) is shown with its trace.

Show the closest matching skipped rule when leftover elements remain
after all rules have been applied. Rules that were tried but skipped
(e.g. optional rules) are tracked and re-evaluated against the first
leftover element, with the best match (by measureProgress) shown.

Show which rules remain unapplied when a CBOR list runs out of
elements, mirroring the existing map validation behaviour.

Replace the old generate-then-deduplicate approach with a stateful
map builder that generates unique keys directly. This handles
occurrence indicators (optional, zero-or-more, one-or-more, bounded)
inline during map construction, retrying key generation on collisions
instead of silently dropping duplicate entries. Required nodes are
sorted first to prioritize generating mandatory entries.

- PTInt generator now covers the full CBOR int range (-2^64 to 2^64-1)
  with anti-gen producing out-of-range values
- Validator now enforces CBOR spec bounds (RFC 8949) for PTInt, PTUInt,
  and PTNInt instead of accepting any integer

Bumps [github.com/fxamacker/cbor/v2](https://github.com/fxamacker/cbor) from 2.9.0 to 2.9.1.
- [Release notes](https://github.com/fxamacker/cbor/releases)
- [Commits](https://github.com/fxamacker/cbor/compare/v2.9.0...v2.9.1)

---
updated-dependencies:
- dependency-name: github.com/fxamacker/cbor/v2
  dependency-version: 2.9.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

Bumps [github.com/blinklabs-io/plutigo](https://github.com/blinklabs-io/plutigo) from 0.1.0 to 0.1.1.
- [Release notes](https://github.com/blinklabs-io/plutigo/releases)
- [Changelog](https://github.com/blinklabs-io/plutigo/blob/main/RELEASE_NOTES.md)
- [Commits](https://github.com/blinklabs-io/plutigo/compare/v0.1.0...v0.1.1)

---
updated-dependencies:
- dependency-name: github.com/blinklabs-io/plutigo
  dependency-version: 0.1.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

The metadatum decoder now only enforces bytes/text size limits (0..64)
for decoder versions > 2, matching the previous SoftForks.validMetadata
behavior. Tests are added to roundTripShelleyCommonSpec so they run for
every era: accepting oversized values at version 2 (Shelley) and
rejecting them from version 3 (Allegra) onwards.

Changes made with the help of an LLM