Investigate Couch Version Management Scripts

[scottbell]

Summary

With #7360 and #7359, we need a way to restrict couch databases to be read only via design documents.

[scottbell]

• New script is needed to apply a JSON export to an existing database. Will create or replace, with NO ID remapping - this is key.
• Two Couch DB users will need to be defined, a "user" and an "administrator". The read-only db will be immutable to anyone but administrators.
• Add design document to make read-only couch readonly to users.

[scottbell]

To test:

1. Set up OpenMCT to use CouchDB following directions here.
2. Start OpenMCT and create a bunch of objects (clocks, plots, etc.).
3. Backup the OpenMCT database following directions here.
4. Login into CouchDB's web interface following directions here.
5. Go into the database, and delete a few of the objects you created.
6. Run the upsert script following the directions here.
7. Go back to OpenMCT, and ensure your deleted objects have been restored.
8. Rename an object in OpenMCT
9. Run the upsert script again
10. Go back to OpenMCT, and ensure your renamed object has been restored to the backup's version.
11. Delete the entire database, and then create it again.
12. Run the upsert script again
13. Go back to OpenMCT and ensure your objects have been restored.