Comment 2 for bug 1579799

Spent a bit of time going back and forth on this with tvoss. We don't want to have a ton of application states, that'll make insanity, but it does make sense for qtmir to drive policy for applications. We don't know completely what that policy is today.

Long story short, the plan is to provide an API that is an enum with known values that can be overridden (it's base type will be int). In this way qtmir can experiment and then we can start to collect the values as we find them to be useful.