The logic for detecting if Chrome Home is enabled has become complex and unruly. It currently handles:

- Promo decision.
- Whether or not the user has set a preference for Chrome Home.
- Basic experiment group (outside of promo).
- Activity restarts.
- Metrics/synthetic trials.

The caching related to native startup can probably be removed since we now have the ability to restart the activity while keeping the active tab alive.