Boost: Create a way to disable page verification for critical CSS.

Page verification allows us to make sure that critical CSS is not generating for an unrelated or WAF page. But, it can also create problems in different situations like, cached pages, redirects that remove the URL parameter, etc. To avoid that, we need to explore if we can disable the page verification on demand.

Start by tracing Boost's critical CSS page-verification flow and how it handles cached pages and redirects that remove the URL parameter. Define an on-demand disable mechanism and verify that page verification can be bypassed only when requested without weakening normal checks.

Written by the indexing model from the issue text.