* Add tests and non-redact criteria for csv validation
* Set redaction rules and test validation for remaining types
* Test that our format test coverage has not slipped
* Test we have defined the redaction logic

The QP sometimes provides a `:source-alias` and no `:join-alias` for
a joined column. Then its MLv2 ref would be missing a `:join-alias` and
it would not match its own column under
`lib.equality/find-matching-column`.

Fixes #36861.

* building out partial graphs

* Set up change deteected modal, graph loading states

* e2e tests. Load admin permissions

* reset permissions from memory on cancel

* fixing types and tests

* add retry to password reset

* fix error case

* add to all emails

* fix misc stuff

* fix test

* fix test

* fix linter

* fix retrying framework

* fix linter

* fix e2e test

* add comment

* adress comments

* fix linter

* fix linter

* fix test

* fix test

* fix test

* fix test

* fix test

* fix e2e test

* fix e2e test

* fix e2e test

* fix test

* fix e2e test and unit tests

* remove paren

* fix linter

* fix e2e test

* fix e2e test

* finally actually fix e2e test

* Use UTF8 encoding for dashboard preview page

* Remove `nonce`

Co-authored-by: adam-james <21064735+adam-james-v@users.noreply.github.com>

---------

Co-authored-by: adam-james <21064735+adam-james-v@users.noreply.github.com>

* Optimize canonicalization of MBQL clauses

Fixes #37245.

This is at the `metabase.lib.js` level. Should help solve some
performance issues where eg. `expressionable-columns` was getting called
on every keystroke for autocomplete; see #37528.

Powered by `metabase.lib.cache/side-channel-cache`, which attaches
the cache in an Atom on a private property mutated onto the `query`.
That means it is invalidated with any edit to the query (since a new
object is returned) and becomes garbage at the same time the query does.

* Support replacing expressions changing types and names

Part of #36211.

Fix TypeError when changing click behavior to drill-through menu & default click behavior does not have selected state (#35863)

* fix: type error on click behavior change

* chore: add comments

* chore: tidy up comments

* chore: reset changes

* add aria-selected & selected drill-through menu assertion

* chore: update assertion comment

* refactor: move aria-selected inside selectable item

* remove 'menu' from click behavior option

* test: add e2e test fro 35354

* chore: clean up demo and update assertion

* refactor: move assertion to existing scenario

* chore: add log on e2e test

* feat: update name for actionMenu

* fix: unknown type in 34845

* fix: test after rebase

* fix: remove unused union type "menu"

* fix: use master version of click-behavior

* fix: readd the tests

* fix: e2e test

* fix: remove set type selector after unset column

* fix: show type selector when click behavior is undefined

* fix: show type selector when finalClickBehavior is default (actionMenu)

* Get rid of Question.prototype.aggregate

* Get rid of Question.prototype.breakout

* Get rid of Question.prototype.filter

This removes the `setDefaultQuery()` method for both
- StructuredQuery and
- Query

Resolves #37506

* Migrate segments in getCardForBlankQuestion and... fix it

* Separate parsing, use Metadata.prototype.segment

* Extract filterBySegmentId

* Migrate metrics in getCardForBlankQuestion

* Rename filterByMetricId to aggregateByMetricId

* Expose segment(query, segmentId) in MLv2, map it in metabase-lib, and use it in initializeQB

* Expose metric(query, metricId) in MLv2, map it in metabase-lib, and use it in initializeQB

* Update Lib.metric and Lib.segment return type

* Break TemplateTag type down to ensure presence of snippet-specific and card-specific properties when dealing with respective snippet types

* Begin migrating updateTemplateTagNames, migrate referencedQuestionIds, migrate updateCardTemplateTagNames

* Migrate hasSnippets

* Remove redundant conditioning

* Migrate updateSnippetNames

* Revert "Break TemplateTag type down to ensure presence of snippet-specific and card-specific properties when dealing with respective snippet types"

This reverts commit f303122055ccf7f50ccf7571cec4c5e7a79c5255.

* Migrate updateSnippetsWithIds & setTemplateTag

* Format code

* Use new updateTemplateTagNames implementation

* Remove old updateCardTemplateTagNames, move and refactor relevant test to initializeQB unit test suite

* Remove no-longer-used NativeQuery.prototype.hasSnippets

* Fix TS issues

* Update initializeQB unit tests

* Revert NativeQuery-related changes in initializeQB

* Rename segment to segmentMetadata & metric to metricMetadata

* landing-page backend validation

* fix spacing

* Handle unknown column-settings keys instead of passing a `nil` key.

The issue #27941 called out pivot table static-viz failing when a sort was added to the column-viz.

This led to a null pointer exception in a formatter when the table render was attempted.
Following the chain a bit, I noticed that there's a map of 'db' keys -> 'norm' keys defined in `metabase.shared.models.visualization-settings`

```clojure
(def ^:private db->norm-column-settings-keys
  {:column_title       ::column-title
   :date_style         ::date-style
   :date_separator     ::date-separator
   :date_abbreviate    ::date-abbreviate
   :time_enabled       ::time-enabled
   :time_style         ::time-style
   :number_style       ::number-style
   :currency           ::currency
   :currency_style     ::currency-style
   :currency_in_header ::currency-in-header
   :number_separators  ::number-separators
   :decimals           ::decimals
   :scale              ::scale
   :prefix             ::prefix
   :suffix             ::suffix
   :view_as            ::view-as
   :link_text          ::link-text
   :link_url           ::link-url
   :show_mini_bar      ::show-mini-bar})
```

Which doesn't contain the key `:pivot_table.column_sort_order`, which is the key added by the frontend when you sort
the column via the viz settings.

This would cause the transform to leave a `nil` key in its place which ultimately led to the NPE further down the
line.

I've made the change that any unknown key gets namespaced with `unknown`. So, `:pivot_table.column_sort_order` ->
`:unknown/pivot_table.column_sort_order`.

This prevents the NPE.

* Use a simpler approach to achieve the same result!

* API Keys: add auth card and manage page

* update deletion copy

* add groups data to snapshot

* update e2e tests to work with backend

* update strings and formatting

* update e2e tests

* remove e2e tests from other pr

* update unit tests

* e2e test update

* mock api key endpoints in settingsEditor unit tests

* remove console log

* use dumb quotes

* handle monospace better

* better form validation

* no need to wait

* update test to work with validation

* contrain table width

* remove monospace variant

* API Keys: Handle Groups UI (#37099)

* API Keys: Show in Group members table

* API Keys: Show count in Group listing

* tweak and test group settings views for api keys

* fix sad lint rebase sitch

* update group manager tests

* better loading behavior

* handle all users api keys

* update types and tests

---------

Co-authored-by: Ryan Laurie <iethree@gmail.com>

---------

Co-authored-by: Ryan Laurie <iethree@gmail.com>

As a follow on to #37546, this fixes an issue in which the macroexpansion of `with-skip-if-empty-pulse-result` doesn't capture the scope of the arguments in `skip-if-empty-test`.

The solution is just to _correctly_ wrap all of the `mt/id` functions in `mt/dataset`.