fix(bug-2060144): resolve google play store bad request error

[kik-kik]

fix(bug-2060144): resolve google play store bad request error

Description

This makes the following three changes:

1. Improve logging of the HTTP error response to make it easier to understand why a request failed.
2. Use a 7 day lag for this job, it appears there is a latency on Google side in making this data available (as of writing the earliest date available is 30th of July).
3. Change the tier tag from tier_2 to tier_3.

[github-actions]

This PR wraps response.raise_for_status() in the six Google Play Store query.py jobs to log the response body before re-raising, moves all seven google_play_store_derived tables to a 7-day scheduling lag, and retags the bqetl_google_play_store DAG from impact/tier_2 to impact/tier_3.

The lag change is consistent for the four vitals_* tables, but the three slow_startup_* scripts apply an additional -1 day shift internally, so the partition they write no longer matches the date_partition_offset being declared — details inline. The error-handling block also calls response.json() on a response that may not be JSON, inside the exception handler.

[lucia-vargas-a]

• comment on removing the timedelta

[scholtzan]

Integration report

• View full diff, if available (SQL + DAGs) (requires private-bigquery-etl access)
• Private CI run
• Bigeye monitoring dry-run: ✅ plan clean — view plan (requires private-bigquery-etl access)