Assignment causes in inspector for attribute values of configuration behave unexpectedly #1445
Description
When a feature model has attributes, the inspector of the configuration editor can be used to inspect and change their values. As the behavior might become quite complex, an extra field AssignmentCause is shown there to indicate why the attribute has its value.
As far as I remember this, the assignment cause should reflect how the value has been determined (manually set by the user, set from default, computed by Z3 optimizer, ...). However, currently it is possible to change the AssignmentCause field manually, which is probably not what should be allowed.
The goal of this ticket is to revisit this functionality, and fix the editor in case there are regressions. See also #1648 for a ticket that might be related.
The fix is needed for mps20241.