CLI additions

[maackle]

PR summary

• adds --uuid option to hc hash
• adds --files option to hc sim2h-client
  • if set, the previous behavior of writing to multiple files applies
  • if not, a single JSON object is printed to stdout

both are needed for what I'm working on, a tryorama check that asserts that client state dumps are consistent with sim2h server state

testing/benchmarking notes

( if any manual testing or benchmarking was/should be done, add notes and/or screenshots here )

followups

( any new tickets/concerns that were discovered or created during this work but aren't in scope for review here )

changelog

• if this is a code change that effects some consumer (e.g. zome developers) of holochain core, then it has been added to our between-release changelog with the format

- summary of change [PR#1234](https://github.com/holochain/holochain-rust/pull/1234)

documentation

• this code has been documented according to our docs checklist

[maackle]

Tests are flaky after merging develop in... app spec failed once, and now stress tests are

[Connoropolous]

@maackle this looks useful!
I have a CLI item high on my wishlist, for hc hash , which is to get a machine readable version of it!

Currently have to do something like this:
hc hash --path dna/acorn.dna.json | awk '/DNA Hash: /{print $NF}' | tr -d '\n'
https://github.com/h-be/acorn-release/blob/f421be88b3e714c1bd5ed81b4addfc36097db025/nix/acorn/default.nix#L11-L12

How is holochain team handling user feedback, feature requests, etc these days?
In my experience, creating github issues isn't very effective.

[maackle]

@Connoropolous I want it to be human-readable too, I think in general we are loose about what we print to stdout so that makes it hard to guarantee. Unfortunately creating an issue may still be the best bet...

[Connoropolous]

I think there was another cli command that had a 'clean' option or something to make it machine readable as an alternative. That's what I was thinking of