cmd/ct-metadata: Design store/update command UX
Some initial ideas to flesh out:
- Stores both downloaded metadata file + signature atomically
- Update an existing metadata+signature file atomically
- Support one or more "santity-checks" before updating, not sure what should be default and explicitly enabled. Examples include: timestamp of newer list is newer; version semantics are correct; log states don't backtrack; etc.