Add encryption support to writing of rhizome content
Add transactions to start and end of rhizome add process
New stress test, rhizome add while transferring
Rhizome extract file will now log an error on hash mismatch
Test each file immediately after adding
Added transaction around file blob creation to ensure rowid is correctly retrieved
Fix transaction error checking
Don't clean up database on every open call
Only assert the file hash matches the file if the payload is not encrypted
Tidy up rhizome extract return code
Re-add database cleanup
Refactor rhizome extract manifest into more useful methods
Extract files based on the manifest id

Renamed rhizome extract file to rhizome dump file
Added rhizome extract file [manifest] [filepath] [pins]
Modified tests to use the appropriate command, assuming that MeshMS payloads will be encrypted
Add offset to nonce instead of replacing byte values
Don't check for duplicates if an existing id has been supplied
Generate version id before reading the file contents
Tidy up rhizome secret handling to improve reusability
Only consider duplicate manifests that we can re-author
Minor improvements to command line time measurements
Enable encryption of rhizome payloads