Component references in settings differ from others

[LourensVeen]

In custom_implementations, we're referring to the component whose implementation to set by model.c1.c2.c3, while for resources and settings we refer to that same component as c1.c2.c3, with the root model implied. That should really be consistent.

For settings this may be tricky. What if we had a model with a submodel implementing model.c1 somewhere, would we then expect an instance in the submodel to look for model.c1.c2.setting, model.c1.setting, model.setting, and setting, or also for submodel.c1.setting and submodel.setting, and if so in which order?

[LourensVeen]

This is resolved for resources, but not yet for settings. Settings are a bit more complicated, because this interacts with various other settings-related things like importing settings and per-component settings. So we'll keep it open for that.