Clarifies which part of the Google link is relevant to Metabase, and modifies some language to better mirror the terms used by Google/OAuth

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

Update tests in accordance with changed geocode API results ("Begles" -> "Talence")

See output of: https://get.geojs.io/v1/ip/geo.json?ip=185.233.100.23

* Emit events outside of db/transaction

When emitting events (particularly revision events), the event handler
loads the item from the db to ensure that all post-processing is
done. If done from inside a transaction, there's a race between the
event handler looking up the object from the db and the transaction
completing to put the item in the db. When the event handler wins, the
following code fails:

```clojure
(push-revision! :entity       Dashboard,
                :id           id,
                :object       (Dashboard id), ;; this is nil
                :user-id      user-id,
                :is-creation? (= :dashboard-create topic)
                :message      revision-message)
```

and then the schema check for `push-revision!` fails `(map? object)`
and there is no event recorded for creation. On edit, it might get the
pre-edit version and record an incorrect message or not create the
revision for the latest change, preventing going back in the future.

I'm only doing this in dashboard but these changes should be audited
and applied everywhere

* Remove `:dashboard-card-update` and `:dashboard-card-create` events

These events were introduced 5 years ago and never have had an event
handler. No worries about race conditions when emitting them from a
transaction if nothing ever cared in the first place.

* Add repro for #15947

* Expand the assertion with the joined table

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

I don't exactly follow what's going on in #15901. But it seems that
the field information can be kept in the db

> ""field_ref"":[""field"",""count(*)"",{""base-type"":""type/BigInteger""}]

And so we need to handle this base type here. Note that in the
function that calls `update-filter-for-field-type` it checks that the
field has a base_type.

I'm also a bit confused by the base_type vs base-type in the above
snippet. But again the calling code has

```clojure
(and (= param-type :dimension)
     (get-in value [:field :base_type]))
(update-filter-for-field-type value)
```

So it seems the field has a base_type rather than a base-type.

* Move unhidden table sync off-thread

* Test bulk hide/unhide syncing

* Check can connect to db and serialize syncs

rather than allowing us to create threads willy nilly, serialize them
and reuse them in a fixed thread pool with a single thread. This helps
if someone "multiple clicks" and launches a few table syncs. It's not
appropriate to use the existing deduplicating stuff in the sync which
prevents later tasks from happening while the current sync step
happens since we want to sync with the most recent changes. So just
serialize them to go one at a time rather than off to the races.

* Clean up ns, make private, and type hints

* Block waiting on table sync to finish

* Use driver.util can connect helper

uses the timeout of 5seconds and catches errors

* disable ToggleHiddenButton during request

Co-authored-by: Dalton Johnson <daltojohnso@users.noreply.github.com>

* Add option to choose between source-folder and test-files in CCI

* Rearrange Cypress files

* Split e2e workflows

* Split native queries into a separate CI group

* Extract `printBold()` function

* Allow multiple `--spec` arguments

* Change 400 errors to 401s on failed authentication

* remove TODO comment

* return 401 for expired JWT in enterprise code

* keep existing exception message when JWT is expired

* fix test failures

* remove comment about timeout on CI that's no longer relevant

* Move assets inside `e2e` folder

* Separate checksum calculation for e2e files

* Fix logo path

* Remove whitespace character from the test title

This ensures that the test is deterministic, i.e not exhibiting different
behavior relative to the current date.

* Merge all enterprise specs together with the OSS ones

* Move whitelabel under `/admin/settings`

* Move specs under `/admin/audit` folder

* Merge `admin/database/add` specs

* Group snippets

* Merge OSS and EE sso specs

* Move sandboxes under `admin/permissions`

* Delete custom drill-throughs spec

* Return boolean value

* Use `Cypress.env` instead of global vars

* Delete empty spec

* Update paths for `eslint` script

[Fixes #8219]

Co-authored-by: Nemanja <31325167+nemanjaglumac@users.noreply.github.com>

* Update notify.clj

* Update auth.clj

Make the load multimethod return a function, which serves as a "reload function", to be called after the first entire pass is complete (via cmd)

Updating various places to combine these functions together and invoke at the top level from cmd.clj when load finishes

Updating dashboard load implementation to check for presence of cards referred to by its dashcards, and if missing, reload those dashboards(s) on a second pass

Splitting out a separate load-dashboards fn that contains the bulk of the body from the previous multimethod implementation (which now delegates to it) to support easier reload functionality

* Fix sidebar loading causes UI jump

* Fix sidebar blinks betweed data refreshes

* Replace `...` with `…` character

* Test collection is open immediately after moving

* Update sidebar children cypress selector

* Add comment about sidebar's loadingAndErrorWrapper

* Fix typo

* Add role props to sidebar and its children