Proposal: Remove SEI threshold when policy ASK is applied.

Context: Site admins shouldn't have to be aware of the SEI implications tied to this particular setting (i.e. the state is hard to describe/ rationalize).  Admins who want a dynamic SEI behavior can simply take the default HBD experience (i.e. we likely will never provide an SEI throttle control).

Background: Historically ASK used to enforce a click to play like behavior.  Removing the SEI threshold check, for this case, would make Chrome behave more consistently with its past behavior.