Cardano Updates

* Add utxo0 binding in UTXOW

For consistency with SUBUTXOW

* Add missing premises

* Improve tc time of Utxo.Computational

Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 6.0.0 to 6.1.0.
- [Release notes](https://github.com/docker/metadata-action/releases)
- [Commits](https://github.com/docker/metadata-action/compare/030e881283bb7a6894de51c315a6bfe6a94e05cf...80c7e94dd9b9319bd5eb7a0e0fe9291e23a2a2e9)

---
updated-dependencies:
- dependency-name: docker/metadata-action
  dependency-version: 6.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Standardizes how aggregators are handled throughout the application,
updating the codebase to use aggregator objects with enhanced metadata
(e.g., `name`, `url`).

Refactored components, tests, and state management accordingly.

Updates scripts and build process to generate an aggregators list, replacing the genesis verification keys logic. Adjusted related files and output to align with the new structure.

Keys are generated per network, with a manual addition for "dev" networks (e.g. e2e).

This fixes all new eslint warnings, mostly `react-hooks/set-state-in-effect`

The doc-slice install-phase strips `share/doc/` from every unit
dir except the target (so a doc slice only ships its own package's
haddocks, not transitively-haddock'd deps).  The target was being
identified by walking the slice's package.db and matching `name:`
on the first conf.

When the doc slice's `depSlices` compose in the corresponding
non-doc slice (it does, so v2-haddock can read `--read-interface`
without rebuilding), `package.db/` ends up with TWO confs for the
target package: the base slice's variant (lndir'd as a symlink)
AND this slice's own --cid (written as a real file).  Bash's
`for f in /path/*.conf` iterates lexicographically, so which conf
the loop matches first depends on alphabetic order of the two
unit-id hashes:

  - 6c5d51e6: this slice's `0ac3cc35` sorts before the base
    slice's `51429f12` → target_uid correctly = this slice's
    --cid → docs preserved.
  - HEAD:     this slice's `bb5ba586` sorts after the base
    slice's `5836f819` → target_uid wrongly = the base
    slice's unit-id → docs in `bb5ba586/share/doc/html` get
    stripped because that unit is treated as a non-target dep.

The transitive cabal-install closure difference between hackage
snapshots happens to flip the lexicographic order of those two
hashes; the underlying bug was always present.

Skip symlinked confs in the lookup, matching the same convention
already used by the `captured store unit` loop at line 1004.
This makes the strip loop key off this slice's own --cid unit
regardless of unit-id ordering.

Verified `tests.sublib-docs.run` on aarch64-darwin native ghc9141.

Signed-off-by: akrepala <[email protected]>

Signed-off-by: Chris Gianelloni <[email protected]>