Use better types for virtual memory translation code

[Timmmm]

Change the VM code from using bits(64) everywhere to using more accurate types. This also enables Sv57 support.

[Timmmm]

I wrote this code quite a while ago and kind of got sidetracked by other stuff, but it looks like I finished it so I thought I may as well push a draft and see what people think. It hasn't been tested extensively yet but I can do that.

One slightly awkward thing I found is that you can use really nice strict types everywhere for the actual translation because the lifetime of sv_width is the scope of the translation function, so it can only have one value. But you can't really do it for the TLB because the lifetime of sv_width for the TLB is infinite so you can end up storing Sv39 addresses in it one cycle and the Sv57 a few cycles later. I just used the widths for Sv57 (the max) and then truncate/zero_extend as appropriate.

[github-actions]

Test Results

396 tests  ±0   396 ✅ ±0   0s ⏱️ ±0s
  4 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit dcb8d5b. ± Comparison against base commit 3707d0b.

♻️ This comment has been updated with latest results.