Cardano Updates

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

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.

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

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.

SUBGOV implementation

Canonical Ledger State: introduce blocks/v0 namespace

New Genric instance were added for BlockIn and BlockOut types,
idea was to use GND to define Arbitrary instance.

Unfortunately currently used version of the QuickCheck does not
have required instances, so instead of defining an instance
there is a comment how to do that once the library is updated.

Use explicit naming in the parameters of the BlockIn type.
This way the user will not be puzzled with their meaning.

Use existing type synonys and rewrite helpers, to make
code cleaner.

Introduced instances for the simplest of the blocks.

This commit defines a new library where the main definitions persist.
In the library there will be definitions for the era angostic types.

As blocks/v0 is common for all eras, it doesn't cripple into the
era libraries.