User Activation Consumption

[mreichhoff]

The API is currently set up to consume activation only in case of explicit user rejection of the permission request. Unfortunately, this means that the rejection occurs in parallel steps and may be modifying state when it shouldn't be. This behavior is modeled after the equivalent in the Storage Access API, and we should consider updating it when/if a feature request for paused user activation goes through.