🛠️ [TASK] : Create a `catalyst-types` crate for our types which are not specific to any particular subsystem

[stevenj]

Summary

The aim is to better fix the dependency tree and maximize reusability of our code

Description

Move the hashes.rs and conversion.rs from the cardano-blockchain-types crate into it.
Move the UUID type from https://github.com/input-output-hk/catalyst-libs/pull/101/files#diff-32b3aff15dee763f3d16014d8f9f3e6c8f33d3b12122c0ffab9c8e3a69cd5fcd

If we have other non-cardano specific enhanced types then we would put them in that crate as well.

from_saturating in conversion.rs should be a public function because we do use that in various places for easy conversion when we know what the ranges are, without the code being a big unwrap() mess.

Anything that not specifically to do with something else or is a simple enhanced type that can be used in multiple places would end up in catalyst-types.

They should not be complex types, they should all be newtypes of some other fundamental type with either more impl implemented on them or canonical cbor encode/decode logic applied to them.