Objects are being persisted with a modified timestamp > persisted timestamp

[akhenry]

Summary

Reported in this comment - #5915 (comment)

Expected vs Current Behavior

Expected: The persisted timestamp on persisted objects should always be later than or equal to the modified timestamp.
Current: Objects are being persisted with a modified timestamp that is later than the persisted timestamp.

Steps to Reproduce

In an Open MCT instance with Couch DB configured (either locally, or in the VIPER test environment):

1. Open Chrome dev tools and open the network tab
2. Clear the current content of the network tab (if not already empty)
3. From the create menu, create a new object of any kind
4. In the network tab in Chrome dev tools find the POST request corresponding to the new object
5. Inspect the payload of the request and verify that the persisted timestamp is >= the modified timestamp.

Environment

• Open MCT Version: 8e3146e
• Deployment Type: Open w/ Couch DB

Impact Check List

• Data loss or misrepresented data?
• Regression? Did this used to work or has it always been broken?
• Is there a workaround available?
• Does this impact a critical component?
• Is this just a visual bug with no functional impact?
• Does this block the execution of e2e tests?
• Does this have an impact on Performance?

Additional Information

[akhenry]

Testing instructions

To verify Object API fix

Follow reproduction steps above to verify that persisted timestamp is always >= modified timestamp.

To test for regressions in Notebooks

This PR also includes changes to the notebook, so please check for regressions in notebooks.

1. Verify that notebooks can be created
2. Verify that sections and pages can be added to, and deleted from notebooks.
3. Verify that entries can be added to, and deleted from notebooks

[ozyx]

Verified fixed -- Testathon 10/27/22

• Verified that created objects have persisted >= modified

Regression tested notebooks. Was able to add/remove/rename sections and pages. Spammed a bunch of entries in multiple notebook pages. No network or console errors were observed.

Clicked through a bunch of payloads from these actions and persisted was always >= modified