* Add test for #15538

* Add extra validation for native source queries

* Add test for sql-source-query validation

* Remove hardcoded project-id from `:bigquery-cloud-sdk` tests

Pull out common helper fn to extract project-id from credentials

Update `bigquery_cloud_sdk_test.clj` to have a var that loads the service-account-json from the env var, then uses aforementioned function to determine project-id

Change sensitive-data-redacted-test to use an arbitrary/fake project-id to remove any sort of confusion

* Fix Migration number 420.00-070 => 42.00-070

* Remove onUpdateSQL

* Log a shortened version of the enterprise token

- when checking that an enterprise token is valid
- test captures the logs, and checks for no token
- in the test, regrettably we print the logs we need to capture

* fix namespace requires order

* remove "Using this URL to check ..." log line

- and update test

* respond to review comments

- no circular dependency with mt, so use that
- "fa3e"*16 -> random token

* print the shortened token one time, and remove let

* truncate legend items

* avoid x ticks overlap

* Add E2E tests

* Allow adding models to dashboards

* Allow using models in native queries

* Fix last edit info vertical alignment

* Change picker's copy

* Handle undefiend question

Fixed by #15555.

Nested Queries Overhaul 2022: Split logic for determining appropriate table & column aliases out of SQL QP (#19384)

This is a safeguard against branch names with special chars which will be replaced by a "-" char

* big query schemas settings

* fix be specs

* Fix drill-through popover look for native datasets

* Enable some drills for fields from native queries

* Reproduce #19180

* Add `cancelQueryOnLeave` prop to NativeQueryEditor

* Don't cancel query when leaving model query editor

* Fix model icons in data picker

* Fix model icons in recent views

* Update the route from `dataset` to `model`

* Update unit tests

* Update e2e tests

* Fix failing e2e tests

* Update collection icon for collection permissions page

* Update collections icon for the serach filter page

* Update the collection icon in the "New" dropdown menu

We have a repo-wide CI run to check ESLint error anyway.
Meanwhile, for day-to-day development of static viz frontend, the main
webpack config is already equipped with ESLint check (along with hot
reload etc).

Trivial trends previously broke. Now they default to basically the ordinary single value viz.

Our email tests can be a bit brittle. Sometimes we assert the first
email in the email inbox is some password reset email, but a race makes
it such that its a "logged in from new ip" email. Othertimes, we might
assert that there are only emails to a particular user but maybe another
test might have triggered an email to another user.

We often might just want two predicates: did the user receive an email
with this subject, or did the user receive an email with this body.

This simply adds those.

It should be safe from races as it can handle emails to multiple users
and multiple emails to the same user.