materialized views don't get updated after deploy

[BenWu]

With the current bqetl tooling, materialized_view.sql only get deployed once and the definitions don't get updated afterwards unless they're manually deleted.

For example, the currently deployed moz-fx-data-shared-prod.firefox_desktop_derived.event_monitoring_live_v1 has DATE(submission_timestamp) >= "2024-05-22" from when it was created but it should be the current date like in the generated sql

bigquery-etl/sql/moz-fx-data-shared-prod/firefox_desktop_derived/event_monitoring_live_v1/materialized_view.sql

Line 93 in 10d2d01

DATE(submission_timestamp) >= "2024-06-18"

Additionally, materialized views don't get deleted when the materialized_view.sql is deleted. We should update the bqetl deploy code so that the deployed objects match what's in the generated sql.

One thing to be careful of is potential costs with recreating a materialized view frequently which might be more expensive than the incremental updates. We should see if it this is relevant for any of the existing views and make sure any generated materialized views have deterministic output.

┆Issue is synchronized with this Jira Task

[BenWu]

Also if this is done, some currently deployed materialized views might suddenly change so we should check the impact of that

[BenWu]

Looks to be fixed by #5640. One thing I just noticed is the most recent merge to main had a dry run failure because a materialized view wasn't found due to being recreated at the same time: https://app.circleci.com/pipelines/github/mozilla/bigquery-etl/36163/workflows/7e17f954-5b8d-4d9d-bbc0-46a7a19ca6a7/jobs/407245/parallel-runs/0

I created #5817 to track this

[BenWu]

#5640 was reverted with #5826