[Canned Reports] Move self-service report views inside batch job instead of ETL

There is one more limitation for self-service reports that I am discovering now.
Self-service reports has two moving pieces.
ETL database
Self-service reports

While we may consider these two items as part of single release but in deployment they may happen independently for any organisation.

e.g.
We create a new xyz_view like (subject_view) and create a report that depends on it.

We deploy to prod.

When the user uses setup or update questions, depending on whether the ETL job has run since then or not for that org - it may fail. We have no control over it.

My suggestion is that:
We move the view creation to the Self-service batch job to avoid this problem.

The issue names self-service reports, the ETL database, and a self-service batch job but no files or tests. Locate the batch-job entry point and the existing view-creation path first; done means view creation occurs in the self-service batch job so report setup or question updates do not depend on an ETL run.

Written by the indexing model from the issue text.