Paul Snow authored Apr 09, 2022 and Ethan Reesor committed Apr 09, 2022

Closes AC-983 "Add functions to smt for duplicating a bpt"

Adds two functions to the BPT
SaveSnapshot
LoadSnapshot

These functions take a file name and, naturally, save or load a snapshot. The value part is up in the air... The assumption is that the hash in the BPT is a key to something in the database that can be loaded to represent the state of the behind the bpt entry's account.

More work may be needed to tune that part of the snapshot.

## Review Checklist

**If any item is not complete, the merge request is not ready to be reviewed and must be marked `Draft:`.**

- [x] The merge request title is in the format `<change type>(<change scope>): <short description>`
  - For example, `feat(cli): add QR code generation`
  - For details, see [CONTRIBUTING.md](/CONTRIBUTING.md)
- [x] The description includes `Closes <jira task ID>` (or rarely `Updates <jira task ID>`)
- [x] The change is fully validated by tests that are run during CI
  - In most cases this means a test in "validate.sh"
  - In some cases, a Go test may be acceptable
  - Validation is not applicable to things like documentation updates
  - Purely UI/UX changes can be manually validated, such as changes to human-readable output
  - For all other changes, automated validation tests are an absolute requirement unless a maintainer specifically explains why they are not in a comment on this merge request
- [x] The change is marked with one of the validation labels
  - ~"validation::ci/cd" for changes validated by CI tests
  - ~"validation::manual" for changes validated by hand
  - ~"validation::deferred" for changes validated by a follow up merge request
  - ~"validation::not applicable" for changes where validation is not applicable

## Merge Checklist

- [ ] CI is passing
- [ ] Merge conflicts are resolved
- [ ] All discussions are resolved