Fixes #5266 - Add a separate view for live user_reports

[ksy36]

This is a follow up for #5250.

I would like to create a separate live view mainly for ML classification job using bugbug that is defined in docker-etl repository.

This ETL job runs every 15 minutes and classifies reports gradually throughout the day. That worked well with the live data, but with the switch to historical table that gets updates only once a day, the script will try to classify all reports at once when they appear in the table. Given the size of the job (800-1k reports with non-empty description per day) this will take a long time, and ETL script likely will not get results during a single run. With this approach, by the time a report appears in the historical table, it will be already classified.

Checklist for reviewer:

• Commits should reference a bug or github issue, if relevant (if a bug is referenced, the pull request should include the bug number in the title).
• If the PR comes from a fork, trigger integration CI tests by running the Push to upstream workflow and provide the <username>:<branch> of the fork as parameter. The parameter will also show up
  in the logs of the manual-trigger-required-for-fork CI task together with more detailed instructions.
• If adding a new field to a query, ensure that the schema and dependent downstream schemas have been updated.
• When adding a new derived dataset, ensure that data is not available already (fully or partially) and recommend extending an existing dataset in favor of creating new ones. Data can be available in the bigquery-etl repository, looker-hub or in looker-spoke-default.

For modifications to schemas in restricted namespaces (see CODEOWNERS):

• Follow the change control procedure

[ksy36]

r? @denschub @scholtzan

[ksy36]

Thanks!