If they're equivalent to the default, they can be removed (for stages)
or replaced by `:all` (on joins).

* Add FormGroupWidget component
* add loading state and placeholder text

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

Noah pointed out that the ApiKey model shouldn't have API-layer bits in it (like referring to the `api/*current-user-id*`), so I made `metabase.api.api-key` populate those fields instead.

... except I forgot to delete the code from the model that populated them as well. Let's do that now.

* Add CopyTextInput component

* add default props

---------

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

* daily automated slack reminders about releases

* fix things that don't work at all

* Update .github/workflows/release-status.yml

Co-authored-by: Uladzimir Havenchyk <125459446+uladzimirdev@users.noreply.github.com>

* make synk happy?

---------

Co-authored-by: Uladzimir Havenchyk <125459446+uladzimirdev@users.noreply.github.com>

The frontend needs the group ID as well as the name, so let's return both in a similar shape as `updated_by`.

When the endpoint is hit, we delete the ApiKey from the database. The
user is left behind to ensure that we don't break foreign keys, and to
enhance auditability.

* Add e2e tests for brush filters in line chart

* Wait for dataset

* debug

* Explicitly set viewport

* Get a bit left

* Shift left

* Do not set viewport

* Revert "Do not set viewport"

This reverts commit b41a039aa85e98b88aa9dba208c304d7f7680979.

* Remove duplicated test

* Add e2e tests for brush filters in map

* Add force

* Simplify assertion

* Specify viewport

* Add internal setting for table render row limit

This change will keep default behaviour of a 10 row limit but allow users to set an env variable to change this default.

* test that table render row limits can be adjusted w/ env var.

Add a test that shows the table render respects the default 10 row limit, and also show that if the user uses the
environment variable `MB_ATTACHMENT_TABLE_ROW_LIMIT`, then they can change the row limit.

* Explicitly unset env. var in the test so it truly tests the default

* Adjust :getter for setting so that defaults are used appropriately

* Fix tests that expected exact text matches on some hiccup nodes

* New default of 20.

* Add a limit of 100 to the rows and add a test for it too.

Wrap `can-append-test` with mt/with-empty-db to fix seemingly unrelated download perms test (#37159)

* Adds a new `metabase.permissions.test-util` namespace
* Adds a new `with-restored-perms!` macro which ensures that permissions are reset after the test body runs
* Updates `with-all-user-data-perms` to use `with-restored-perms!` under the hood, and renames it to `with-all-user-data-perms!`

This is my attempt to fix the state issues with permission tests in a more robust way. Generally, the `permissions` and `sandboxes` tables aren't too large, so it shouldn't be a ton of overhead to just fully reset these tables after a test runs—and certainly doesn't compare with the time lost to debugging state issues between perms tests. (I actually saw this test namespace run one second _faster_ with these changes, in a very unscientific test.)

I'm planning on adding more utils to the `metabase.permissions.test-util` namespace to make perms tests easier to write. But want to keep this PR focused on the change that will (hopefully) fix the tests failing on master.

Fixes #37129.

quesiton ---> question

* Match SparkSQL database-type case insensitive

* Use lower-case-en to match SparkSQL database-type

---------

Co-authored-by: Bas Beelen <bas.beelen@channable.com>
Co-authored-by: lbrdnk <lbrdnk@users.noreply.github.com>

* Compare parameters in fetchDataCards to clearCache
* Fix click-behavior suite
* Add tabs/card loader e2e test
* Add a comment
* Update test name to include issue number

Ignore another clj-kondo library config missed by https://github.com/metabase/metabase/pull/36889

This was causing dirty changes to be left in the repo after running `bin/kondo.sh`. The script should be clean after this change, I think.

Fixes misc clj-kondo errors in tests (and one random whitespace issue in a src namespace).

* Upgrade chromatic

* Revert back to NODE_ENV

* Sync storybook packages

* Replace imports from clients-api to addons

Add delay instead of throttle.

Fixing a flake analyzed in this document.
https://replayio.notion.site/dashboard-filters-reproductions-25322-loading-list-19324262f19d404ba03787c9f70968ab

The test `25322-loading-list-values.cy.spec.js` has become flaky because the period of time to find loading-spinner element is too short. This is thanks to API response being fast.

in the past, this was partially remedied by adding `setThrottle()` method to slow the API response down. while it is a good initial approach, it is not resilient to a situation when the data transfer size becomes smaller.

I’m suggesting changing the method to setTimeout that will give the test enough time to catch the loading state.

In the future, this particular test would be a good candidate for a component test as it is quite granular.

From the maintainer: "includes a fix for a bug your tests were hitting in a couple places".