feat: new command for inspecting state-root mismatches

[lemmih]

Summary of changes

Changes introduced in this pull request:

• forest-tool archive diff replaces forest-cli state diff.
• The new command is more ergonomic and doesn't require copy&pasting CIDs.

Example output (with Forest modified to use an incorrect base-fee):

$ forest-tool archive diff forest_snapshot_calibnet_2023-10-11_height_989049.forest.car.zst --epoch 989000
- Expected state hash: bafy2bzaceaujrn4wf72j6ojgnka47lkdxzttxv22brjteaexs76vtgfptebfe
+ Computed state hash: bafy2bzacecgggv4fd27pfs3xzxg764kcaj6otf5sar5ypt7r22qn66xmotb74
Address t099 changed: 
 ActorState(ActorState { code: Cid(bafk2bzacebor5mnjnsav34cmm5pcd3dy4wubbv4wtcrvba7depy3sct7ie4sy)
  state: Cid(bafy2bzacedpuk5ggwoq3s2wixsyjjnexpsjstdlyntio76vs2lt2jvy3o6mau)
  sequence: 0
- balance: TokenAmount(13369711.247500476309337237)
+ balance: TokenAmount(13369711.247500461221402237)
  delegated_address: None })
V11(State { address: Address { payload: ID(99) } })
Address t035181 changed: 
 {
  "code": {
    "/": "bafk2bzacedrbpvjvyzif2cjxosm4pliyq2m6wzndvrg7r6hzdhixplzvgubbw"
  }
   "sequence": 33965
-  "balance": "165.580950032976185226"
+  "balance": "165.580950048064120226"
   "state": []
}

Reference issue to close (if applicable)

Closes #3586

Other information and links

There is no testing since there are no convenient ways of triggering state-root mismatches.

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

[jdjaustin]

It would be nice to have some documentation of this feature in the developer documentation

[LesnyRumcajs]

Can you contrive some test cases, or would that be too time-consuming or complex?

[lemmih]

Can you contrive some test cases, or would that be too time-consuming or complex?

I have no idea how to test this. We have tests for pretty-printing diffs but I don't see an easy way of doing end-to-end testing.

[ruseinov]

Looks good to me. As a follow-up would be great to have this tool more exposed by means of public-facing docs.
There are also no tests, but it's not a blocker.

[LesnyRumcajs]

For completeness, let's write how to perform this conversion.

[lemmih]

Done.

[LesnyRumcajs]

We could document this as well.

[lemmih]

Done.