Show feature's supervisor option in inspector

[AlexKrupa]

💡 Motivation

#95

🧑‍💻 Changes

Simple approach which looks like this:

Notes:

• Enum-like format (i.e. ChristmasTheme.Enabled) is easily understandable for both devs, QA and other folks.
• Used standard padding and same text appearance as description. I played a bit with smaller (4dp) padding between feature name and supervisor but it didn't really make a difference. Also tried customizing the text appearance (e.g. Subtitle2), but in the end making it uniform with description looked best. 🤷‍♂️ Suggestions welcome though.
• The word Supervisor could potentially be changed to something else as the nomenclature is not that obvious for non-devs. Alternatives: "dependent on", "controlled by", "controllable if", etc. What do you think?

📝 Checklist

• I updated the changelog.
• I updated the documentation.
• I updated the sample.

🧪 How to test

Run the sample app. Optionally other parameters (such as description) can be added to see what it looks like.

🔮 Next steps

Either the issue can stay open or I can create a new one for improving the UI, e.g. showing supervised features in some kind of a tree hierarchy.

[MiSikora]

Thanks for the PR. I left few comments.

Also tried customizing the text appearance (e.g. Subtitle2), but in the end making it uniform with description looked best. 🤷‍♂️ Suggestions welcome though.

It looks good to me as is.

The word Supervisor could potentially be changed to something else as the nomenclature is not that obvious for non-devs. Alternatives: "dependent on", "controlled by", "controllable if", etc. What do you think?

Leaving supervisor is ok with me but I get your point. I would avoid X if because it might be confusing when X happens to be an option on a feature. If you want to change it I would either use controlled by or maybe something like Turned on if %1$s is %2$s. The latter might look better in italics.

Either the issue can stay open or I can create a new one for improving the UI, e.g. showing supervised features in some kind of a tree hierarchy.

Issue can stay open, I'll just update it after merging this PR.

[AlexKrupa]

I'll leave the string template as is.

[MiSikora]

LGTM.

You'll just need to fix SyntheticAccessor Lint issue.