Scenario Manager: Support symlinks in for component configs

Features:

1. If a component.cfg file is a symlink, do not write delete + create it. (In other words: When deleting+writing a .cfg file, assert that it is not a symlink).
2. Prevent the user/GUI from trying to update/change a .cfg file if it is a symlink. More precisely, if component.cfg is a symlink:
   • make the property editor (right hand side) read-only
   • Add label to notify user that this is a read-only view because the config from another scenario is being reused. Tell them that to edit the config, they should open the other scenario and edit it there
   • In addition, provide a button that creates a copy of the independent config in this scenario to make it writable. Try to make clear that this will result in two independent copies of the config, so changes in <linked scenario> will not affect this scenario and vice versa.

Corresponding MR is !90 (merged)