Condition widgets are causing persistence conflicts with Couch DB

[akhenry]

Summary

Condition widgets cause persistence conflicts when viewing them, or when viewing a layout that contains persistence widgets. This is because they persist their state even when nothing has changed.

Expected vs Current Behavior

Condition widgets should not persist their state unless it has been changed. Currently persistence widgets (and possibly sets) use mutation to establish initial model state when they load, even when they're not being edited. If more than one person views a condition widget (or a layout containing it) then a conflict can occur.

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?

Steps to Reproduce

See VIPEROMCT-60 for detailed reproduction steps.

Environment

• Open MCT Version: 1.7.8
• Deployment Type: VIPER Stable
• OS: Mac OS
• Browser: Chrome

[akhenry]

Closing as dupe of #4146