Cardano Updates

Signed-off-by: Yurii Shynbuiev <[email protected]>

# Conflicts:
#	catalyst_voices/packages/internal/catalyst_voices_models/lib/src/campaign/campaign.dart

Signed-off-by: Yurii Shynbuiev <[email protected]>

Previous implementation was wrongfully iterating just over the vector of
values, which itself is lazy, causing unexpected thunk buildup.
Technically it is a nice optimization, since that would mean there is no
iteration over the vector of keys, however, without forcing everyone to
switch to newest version of `vector-0.13.2.0` that introduced
`Data.Vector.Strict` we cannot have a strict `map` (using `mapM` is out
of the question, since it has terrible perfomrance)

This commit also adds strictness tests for `map` and `mapWithKey` and a
`noThunks` instance for future compatibility

Somehow whenever `StakePoolsSnapShot` is created there is a thunk that
gets into it. I can't quite figure out what is causing it, but
concidering it only happens during generation of arbitrary data and for
the initial test state this shouls be fine foce 'em. It would be nice to
get to the bottom of this, since theoretically thunks should not be possible
in `VMap`. Potentially switching to using a strict tuple could help.

That field being lazy could not lead to space leaks, but it was forced
upon construction of `SnapShot` anyways, since another strict field
`spssStakeRatio` used this value upon construction.
Therefore, for simplicity and consistency sake it makes sense to keep
this field strict.

Change Predicate failure with UTxO to NonEmptyMap

+  changed globalScripts type; fixed Transaction docs
+  revise doc prose in Utxo module
+  rebase fixes
+  rewrite premises of UTXO rule

   +  **No overlapping spends across subtransactions and top-level tx**: add explicit pairwise-disjointness premise for batch spending inputs.

   +  **Reference-script/self-usable-output concern**: move reference-input validation to batch output view so reference inputs may point to outputs from full batch (including its own outputs), while keeping spending inputs mempool-safe against utxo₀.

clean up and correct consumed/produced accounting