Add and persist slot_number and block_hash to CardanoTransaction

[Alenar]

Content

This PR add two new fields to our CardanoTransaction type: slot_number and block_hash. This will allow comparison between a transaction and their incoming beacon that will include them (and the block_number that's already a part of our transaction type).

Pre-submit checklist

• Branch
  • Tests are provided (if possible)
  • Crates versions are updated (if relevant)
  • Commit sequence broadly makes sense
  • Key commits have useful messages
• PR
  • No clippy warnings in the CI
  • Self-reviewed the diff
  • Useful pull request description
  • Reviewer requested
• Documentation
  • Update README file (if relevant)
  • Update documentation website (if relevant)
  • Add dev blog post (if relevant)

Comments

To update the database provider part of the mithril-signer we simply copy-pasted the update one from the aggregator, adapted the import and removed the part that implemented traits not defined in the signer.
We choose to keep all the remaining code even if it's not used in the signer in order to keep as much as possible a parity between the aggregator and the signer file as long as they're still manipulating the same data.

Issue(s)

Relates to #1591

[github-actions]

Test Results

    3 files  ±0     42 suites  ±0   10m 14s ⏱️ + 1m 40s
  946 tests +3    946 ✅ +3  0 💤 ±0  0 ❌ ±0 
1 040 runs  +3  1 040 ✅ +3  0 💤 ±0  0 ❌ ±0 

Results for commit a869994. ± Comparison against base commit 0d4cace.

♻️ This comment has been updated with latest results.

[jpraynaud]

LGTM 👍

[dlachaume]

Just two comments, otherwise LGTM 🚀