Consistent component API desgin

[domtronn]

We have some components that have optional 'features', for example, optional progress bars or optional images. I think we should have a consistent approach to designing these kinds of APIs, and my initial food for thought w.r.t. options are the following;

1. Opt in - i.e. showFeature={true|false}, explicitly asking for the feature
2. Opt out - i.e. hideFeature={true|false}, explicitly remove the feature
3. Implicitly - i.e. infer whether to render component based on presence of data

Regardless of which one we choose, I think we should follow one approach for all components and refactor the existing ones accordingly.