* Validate datasets are found when checking bigquery

Fixes #19709

* Address PR feedback

Made a general mechanism to pass expected messages to users in
api/database via ex-info. This allows us to suppress logging for
"unexceptional" exceptions that one can expect to hit while setting up
drivers.

* Only validate when filters are set

Also removed the dataset list from the exception as it's not surfaced to
users.

* scaffolding, docstring & arg parsing

* tweaks

* registry and basic oss->ee dispatch

* stubbed defenterprise-ee

* full defenterprise-ee impl

* fix build and tweak docstring

* remove debug code

* basic tests

* use defonce

* support for :any feature

* schema support

* fix schema test

* switch to using format

* support for schema on return val

* tweak macro

* move schema validation to submacros

* do ee fn resolution at runtime

* do conditionals at macro-expansion time

* adjust semantics & refactor

* fix test

* add memoization for ee resolution

* fix tests

* emit register-mapping! call to avoid eval

* call starts-with on symbol

* remove schema support

* use spec for arg parsing, generate fns, and remove :error fallback option

* clean ns

* change schema alias to schema

* add :arglists meta and small refactor

* refactor

* move EE logic to fn

* validate that the correct args are passed in EE/OSS namespaces, and make :feature required

* remove logic for handling nil :feature

* fix lint errors

* fix ee macros

* defenterprise-schema macro & tests

* clean ns

* propogate metadata

* don't memoize ee resolution in dev to make debugging easier

* dont do ee fn resolution during macroexpansion

* minor refactor and cleanup

* major refactor

* update docstrings

* more docstring tweaks

* try to fix lint error on ldap PR

* use dan's suggestion

Sometimes you’ll make a change to some code and not want to commit it. You probably add a comment to the code and hope you’ll either see the comment in the diff before committing or just remember not to check in the change. If you’ve ever done this you’ve probably also committed something you didn’t mean to commit. I know I have.

Below is a git pre-commit hook that searches for the text `nocommit` and if found rejects the commit. With it you can stick `nocommit` in a comment next to the change you don’t want committed and know that it won’t be committed.

You can maintain a list of personal forbidden words by exporting
`NOCOMMIT_RE` e.g:
`export NOCOMMIT_RE="spy|tap>|curse word"`

This issue has a simple fix but a convoluted story. The new bigquery
driver handles multiple schemas and puts that schema (dataset-id) in the
normal spot on a table in our database. The old driver handled only a
single schema by having that dataset-id hardcoded in the database
details and leaving the schema slot nil on the table row.

```clojure
;; new driver describe database:
[{:name "table-1" :schema "a"}
 {:name "table-2" :schema "b"}]

;; old driver describe database (with dataset-id "a" on the db):
[{:name "table-1" :schema nil}]
```

So if you started on the new driver and then downgraded for some reason,
the table sync would see you had tables with schemas, but when it
enumerated the tables in the database on the next sync, would see tables
without schemas. It did not unify these two together, nor did it archive
the tables with a schema. You ended up with both copies in the
database, all active.

```clojure
[{:name "table-1" :schema "a"}
 {:name "table-2" :schema "b"}
 {:name "table-1" :schema nil}]
```

If you then tried to migrate back to the newer driver, we migrated them
as normal: since the old driver only dealt with one schema but left it
nil, put that dataset-id on all of the tables connected to this
connection.

But since the new driver and then the old driver created copies of the
same tables, you would end up with a constraint violation: tables with
the same name and, now after the migration, the same schema. Ignore this
error and the sync in more recent versions will correctly inactivate the
old tables with no schema.

```clojure
[{:name "table-1" :schema "a"}  <-|
 {:name "table-2" :schema "b"}    | constraint violation
 {:name "table-1" :schema "a"}] <-|

;; preferrable:
[{:name "table-1" :schema "a"}
 {:name "table-2" :schema "b"}
 {:name "table-1" :schema nil :active false}]
```

* [E2E] Create and run new `organization` CI group

* Run `organization` group in CI

* Remove `moderation` from the PR check

* Extract specs related to `fitlers` in a separate folder

* Run new `filters` E2E group in CI

* show when users don't have access to foreign table fields data model

* change copy

* Update dashboard link in README

This PR updates the dashboard link in the README from `answers` to `dashboards`

* more www

Co-authored-by: Jeff Bruemmer <jeffbruemmer@gmail.com>

Fixes #19860

SNAPSHOT tables in bigquery hold diffs from an underlying table:
https://cloud.google.com/bigquery/docs/table-snapshots-intro. But the
support in the sdk only came in 1.135.0 :
https://github.com/googleapis/java-bigquery/blob/main/CHANGELOG.md#11350-2021-06-28

I picked the most recent 1.135 version.

Running

```shell
clj -A:dev:ee:ee-dev:drivers:drivers-dev -Stree
```

Shows conflicts on

```
X google-http-client-jackson2 1.39.2 :older-version
; using 1.39.2-sp.1 from google analytics

X com.fasterxml.jackson.core/jackson-core 2.12.3 :older-version
; from cheshire we have 2.12.4

X com.google.http-client/google-http-client 1.39.2 :superseded
; using 1.39.2-sp.1 from google-http-client-jackson2 (1.39.2-sp1)

X commons-codec/commons-codec 1.15 :use-top
; pinned to this version at top level

X com.google.guava/guava 30.1.1-android :use-top
; pinned to 31.0.1-jre top level
```

So I think this change is quite safe. After the release we should
investigate the breaking changes that come in the 2.0.0 release and look
into getting onto 2.10.10. This version worked locally for me but I
don't want to introduce that into the release just yet.

* Remove right click option when unable to write to collections

* Permissions for snippets root requires :namespace key on the collection

* pr feedback

Co-authored-by: Case Nelson <case@metabase.com>

* Only allow bulk invalidation when there are things to invalidate

* Updating test

* human readable weird logic

* Update frontend/test/metabase/scenarios/question/reproductions/17910-revision-history-update.js

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

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

* build pot file

* update translations for 0.43

* hide custom mapping for users with no permissions

* remove log

```
❯ clj-kondo --lint src:shared/src
src/metabase/api/common/validation.clj:2:33: warning: Inconsistent alias. Expected str instead of string.
src/metabase/api/database.clj:664:5: warning: Redundant let expression.
src/metabase/api/table.clj:18:45: warning: Inconsistent alias. Expected field-values instead of sync.field-values.
src/metabase/cmd.clj:123:5: warning: unused binding docs
src/metabase/db/data_migrations.clj:15:52: warning: Inconsistent alias. Expected perms-group instead of group.
src/metabase/db/data_migrations.clj:55:15: warning: #'metabase.db.data-migrations/data-migrations is deprecated
src/metabase/db/data_migrations.clj:62:24: warning: #'metabase.db.data-migrations/data-migrations is deprecated
src/metabase/db/data_migrations.clj:63:7: warning: #'metabase.db.data-migrations/run-migration-if-needed! is deprecated
src/metabase/db/data_migrations.clj:154:1: warning: #'metabase.db.data-migrations/defmigration is deprecated
src/metabase/db/data_migrations.clj:201:1: warning: #'metabase.db.data-migrations/defmigration is deprecated
src/metabase/db/setup.clj:59:5: warning: Missing catch or finally in try
src/metabase/driver/postgres.clj:18:63: warning: Inconsistent alias. Expected sql-jdbc.describe-table instead of sql-jdbc.sync.describe-table.
src/metabase/driver/postgres.clj:304:9: warning: unused binding nfc-path
src/metabase/driver/postgres.clj:323:60: warning: unused binding fields-fields
src/metabase/driver/sql_jdbc/sync/describe_table.clj:253:39: error: Expected: set or nil, received: seq.
src/metabase/driver/sql_jdbc/sync/describe_table.clj:254:39: error: Expected: set or nil, received: seq.
src/metabase/driver/sql_jdbc/sync/describe_table.clj:333:11: warning: unused binding map-inner
src/metabase/models/secret.clj:248:23: warning: use :else as the catch-all test expression in cond
src/metabase/pulse/render/body.clj:216:64: warning: unused binding cols
src/metabase/task/refresh_slack_channel_user_cache.clj:52:25: error: clojurewerkz.quartzite.schedule.simple/with-interval-in-seconds is called with 1 arg but expects 2
linting took 5988ms, errors: 3, warnings: 17
```

```
❯ clj-kondo --lint src:shared/src
src/metabase/task/refresh_slack_channel_user_cache.clj:52:25: error: clojurewerkz.quartzite.schedule.simple/with-interval-in-seconds is called with 1 arg but expects 2
linting took 5270ms, errors: 1, warnings: 0
```

Want to call out a few things:

The following all related to the new paths into json feature. Wanted
howon to verify that nothing got dropped with these unused bindings.

```
src/metabase/driver/postgres.clj:304:9: warning: unused binding nfc-path
src/metabase/driver/postgres.clj:323:60: warning: unused binding fields-fields
src/metabase/driver/sql_jdbc/sync/describe_table.clj:253:39: error: Expected: set or nil, received: seq.
src/metabase/driver/sql_jdbc/sync/describe_table.clj:254:39: error: Expected: set or nil, received: seq.
src/metabase/driver/sql_jdbc/sync/describe_table.clj:333:11: warning: unused binding map-inner
```

* explain what is going on during encryption key rotation
* better argument error handling for commands

* fix dashboard serialization+deserialization

* remove dashboard shortcuts back button

* update datetime filter serialization code for starting from/exclude

* remove disable startingFrom/Exclude props

* fix unit tests

* fix unit tests

* Don't turn read-only queries into ad-hoc ones

* Allow reordering table columns for no-data users

* Handle URL change on viz changes for no-data users

* Don't show "rerun overlay" for no-data users

* Don't show "rerun overlay" for no-data users

* Don't show "Save" button on read only questions

* Allow changing viz settings locally for no-data

* Add e2e tests

* Fix no-data user can't use parameters

* Remove #9772 repro

* Fix "Save" button

* Fix read-only column resizing test

* Fix #18433