Cardano Updates

The trace messages that get emitted differ between debug and release
builds. Therefore, running the same test (with the same golden file of
expected trace messages) both for debug and release builds will cause
problems. To avoid these, we now have two separate tests, each with its
own golden file, and only run the appropriate one depending on the build
type.

The only reason this did not lead to problems so far is that the test
only inserted four entries into the table, not triggering any
interesting internal events. However, we *will* emit internal messages
once we start migrating the union level when a union is paid off (or we
decide to test more interesting operations). Since we now can, I made
sure that these tests now at least trigger the creation of a merge.

Allow table levels to be empty

Release `blockio-0.1.1.2` and `lsm-tree-1.0.0.2`

Ironically, while writing a property test for the `RunIxKeyIx` pattern synonym
that had a typo in a bit-mask (see #841), we included that same typo in the shrinker for
that property test. Hopefully these typos are now fixed once and for all!

Fix a typo in a bit-mask in `unpackRunIxKeyIx`

This typo effectively limited the number of bloom queries we could perform on a
single run to 4096 (hexadecimal: 0xfff), while the limit should have been 65536
(hexadecimal: 0xffff). So under high lookups workloads, this limit would be hit
and result in erroneous bloom query results

This shows that there is a bug in the pattern synonym

The trace messages that get emitted differ between debug and release
builds. Therefore, running the same test (with the same golden file of
expected trace messages) both for debug and release builds will cause
problems. To avoid these, we now have two separate tests, each with its
own golden file, and only run the appropriate one depending on the build
type.

The only reason this did not lead to problems so far is that the test
only inserted four entries into the table, not triggering any
interesting internal events. However, we *will* emit internal messages
once we start migrating the union level when a union is paid off (or we
decide to test more interesting operations). Since we now can, I made
sure that these tests now at least trigger the creation of a merge.