UTxO-HD: add tables to mock ledger

[jasagredo]

Description

Every test that used to run with SimpleBlocks now uses tables

Checklist

• Branch
  • Commit sequence broadly makes sense
  • Commits have useful messages
  • New tests are added if needed and existing tests are updated
  • If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
  • If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
  • If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.
• Pull Request
  • Self-reviewed the diff
  • Useful pull request description at least containing the following information:
    • What does this PR change?
    • Why these changes were needed?
    • How does this affect downstream repositories and/or end-users?
    • Which ticket does this PR close (if any)? If it does, is it linked?
  • Reviewer requested

[jasagredo]

Already well known pattern of:

diff . unstow . apply . stow

[dnadales]

Good point. I find that in every instance where we have to perform stowing/unstowing, applying, and diffing it's hard to track what's going on and why. I wonder if it'd make sense to abstract this away.

[jorisdral]

Looks good to me!

Note: there are some lines that exceed ~80-ish characters, I placed some suggestions to spread them out over multiple lines, but I haven't done that everywhere

[dnadales]

We should probably asses the impact this has in testing time (just run the test before and after to see if there is a significant diff).

I think the changes of the mempool simplification are also here, right, so I skipped those. But let me know if I should review those.

[dnadales]

Good point. I find that in every instance where we have to perform stowing/unstowing, applying, and diffing it's hard to track what's going on and why. I wonder if it'd make sense to abstract this away.

[jasagredo]

We also need to check if there is an increase in the running time of the tests for introducing this.

[jasagredo]

test-consensus

feature/utxo-hd

All 59 tests passed (29.12s)
	User time (seconds): 25.58
	System time (seconds): 0.33
	Percent of CPU this job got: 87%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0:29.48
	Maximum resident set size (kbytes): 280364

jasagredo/add-tables-to-mock-ledger

All 59 tests passed (28.44s)
	User time (seconds): 24.36
	System time (seconds): 0.36
	Percent of CPU this job got: 85%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 0:28.80
	Maximum resident set size (kbytes): 198016

Remarks:

• notable memory decrease to 2/3.
• roughly equivalent running time.

ouroboros-consensus-mock-test

feature/utxo-hd

All 37 tests passed (94.93s)
	User time (seconds): 94.37
	System time (seconds): 0.96
	Percent of CPU this job got: 100%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 1:35.28
	Maximum resident set size (kbytes): 221724

jasagredo/add-tables-to-mock-ledger

All 37 tests passed (112.14s)
	User time (seconds): 111.27
	System time (seconds): 1.30
	Percent of CPU this job got: 100%
	Elapsed (wall clock) time (h:mm:ss or m:ss): 1:52.50
	Maximum resident set size (kbytes): 248692

Remarks:

• Similar memory usage
• Time increase. It is consistent (tried again) but it is like 10% only, I think it is acceptable. If we wanted we could suppress the output of the threadnet tests and this should make it even faster.