UI for ignoring and overriding contributed AADL is confusing

[lwrage]

Checking a the checkbox next to the property set disables its processing. It would be better to initially have all boxes check and have the user uncheck the ones that should be ignored.
Overriding is unintuitive: One needs to select the file in the tree and click the override button. Also, there is no indication in the tree that a file is overridden.
It should not be possible to ignore AADL_Project.

[AaronGreenhouse]

Discussed this with @lwrage. The plan is to

• Remove the checkbox column. Instead, there will be three buttons on "Disable", "Override", and "Restore". This way, it will not be possible to disable an overridden property set. This eliminates the confusing use of the check box. The property set AADL_Project will not be able to be disabled.
• The status line that shows the location of the contributed property set will be replaced by a second a "Status" column in the table that reads either "Disable", "Contribute by ", or "Overridden by ". This also replaces the inconsistent decorators of "[Overridden]" and "(disabled)" that are added to the property set label.
• The text in the dialog box should be more descriptive and indicate that it is not possible to be both overridden and disabled.
• The text in the "Property Set" pane is confusing and needs to better describe what is going on
• Status line of a contributed resource in the "AADL Navigator" needs to indicate if the resource is disabled
• Update the OSATE documentation.