* initial changes

* possible fix

* escape markdown

* remove string

* use existing function

* fix tests

* fix test

* fix test

* only change headings

* remove log

* update tests

* update test

* update test

* update tests

* update test

* address comments

* Preserve filters during navigating back to dashboard (#32142)

* Clearly call dashboard actions

* Add proptypes and update return type of the hook

* Reorder props

* Preserve filters on navigating back to dashboard

* Add e2e test

* revert not needed change

* Verify the data is re-requested after navigating back to dashboard

* Restore tab during navigating back to the dashboard (#32147)

* Do not reset tab to be able to return back to it via back button

* Improve test perf

* Verify back button navigates to previous tab with e2e

* Fix places causing warnings in dev console and tests (#32196)

* Fix places causing warnings in dev console and tests

* Fixup

* Add warning message when leaving an edited, existing SQL question

This PR adds this functionality that's supposed be a part of
an epic https://github.com/metabase/metabase/issues/29421

* Use similar structure on other part that rely on the same logic

* Fix condition to show browser prompt + add tests

* Prevent passing new props to QueryBuilder

Since those props will be pass down to other children, and they won't be
used anyway. Those new props are only used in this file.

* Make test setup more concise

* Address review: Change from util function to selector

* Address review: move hook to sector and move selector tests to component test

* Fix failed unit tests from merging `master`

* sort dashboard cards for mobile

* unit test sorting logic

* Add unmount handler for InputBlurChange

* Fix e2e tests

* make the field values widget a functional component

* fix debounce

* fix loading field values without mutable props

* update FetchFieldValues mock

jsdom lib had a perf problem with getComputedStyle method, which is used a lot with css in js solutions. The problem was addressed in JSDOM 22.1.0, but jest itself waits for the major upgrade to take it into account. The temporary proposed solution is to use yarn resolutions.

* add mb to upload limit tooltip

* bigger MBs

* put search enhancements under content-management flag

* fix token check for snippet perms and add with-additional-premium-features macro

* remove :feature :any option for defenterprise

* fix whitespace in docstring

* fix snippet API tests

* fix final tests

* fix feature for snippets, plus some small test fixes

* fix more tests

* Clean ns

Before
WARN api.common :: Unexpected parameters at [:post "/"]: [:description :collection_id :name]

After
WARN api.common :: Unexpected parameters at [:post "/api/dashboard"]: [:description :collection_id :name]

* Fix missing `slack_colorized` icon

* Convert `NewPulseSidebar` to TypeScript

* Add `getFields` method to `Database`

* Ensure only real fields returned by `getIdFields`

* Rework to iterate over fields

* Add repro

* Add scrollableHorizontally & scrollableVertically chai properties

* Use scrollableHorizontally in table test suite

* Take border width into account when computing scrollability

* Add an e2e test for #28788

* Remove debugging info

* Change "to.not.be" to "not.to.be" to be consistent

* Simplify test

* Improve the test case as the overflow also can come from the collection description

* Fix #28788

* Format test

* Replace custom chai assertions with custom helpers

* refactor `useDashboardTabs` and `useSyncURLSlug` to not nullify `selectedTabId` on unmount

* remove unused code

* fix slug not updating in edit mode

* add unit test case

* [MLv2] Native query functions for changing db and collection-name

* Rename feature to be more specific

* Use native-extras based on feedback

* Fix missed rename

* create measureTextWidth functions

* update rowChart and utils

* update static viz

* Make bucket pickers more customizable

* Allow hiding expressions in `AggregationPicker`

* Migrate `SummarizeSidebar` to MLv2

* Delegate more stuff to aggregation components

* Polish for breakout components

* Don't copy queries into sidebar state

* Use two breakouts in sidebar tests

* Use long display name for pinned breakouts

* Fix "replace column" used instead of "add column"

* Fix extra spacing

* Fix tooltip position

* Fix pinned breakouts display

* Fix E2E test

* Clean up bucket pickers

* Fix types

* Fix border width

* Simplify `BreakoutColumnList`

* Add `withDefaultBucket` helper

* Avoid `byRole` queries in sidebar tests

* Fix UI jumps while searching

* Hide "Custom expression" option

* Fix #31339

* Add an e2e for horizontal scrollbar presence

* Add an e2e test for the originally reported issue #31339

* Remove inline headerCells

* Format tests

* Remove redundant code

* Move tests to table visualization scenarios tests suite

Adding filter of summarized field grouped by latitude and longitude on a map changes visualization type (#31646)

* Take sourceQuery into account if StructuredQuery does not have any aggregations or breakouts when determining Question's default display
- It's an attempt to fix #30057

* Don't check source query for models

* Use source query breakouts and aggregations to determine default display only if the question does not have any breakouts, aggregations, and joins
- Make the condition to always use "table" display for Models more prominent

* Revert first attempt

* Introduce CardObject and fix displayIsLocked typing

* Refactor maybeUnlockDisplay into maybeResetDisplay

* Revert "Introduce CardObject and fix displayIsLocked typing"

This reverts commit 770e7a50d3b9f381741ba7cb1655c1d9be5f295c.

* Improve diff

* Update unit tests after maybeUnlockDisplay to maybeResetDisplay refactoring

* Update maybeResetDisplay unit tests

* Improve test case names

* Add tag for the test that reproduces the issue

* Add test for issue #30057
- use visualize() helper
- extract addCountGreaterThan2Filter()

* Add a test case for adding columns

* Add a test case for removing columns (resetting to default value)

* Add a test case for adding aggregations

* Add another test case

* Reuse e2e helpers
- add missing "field" parameter support in addSummaryGroupingField
- add removeSummaryGroupingField

* Remove redundant condition

* Update issue id in tests after extracting separate GitHub issue

Fixes #32026.

* Refactor: move operator stuff into separate namespace

* Filter operator overhaul

* display-name and long-display-name

* Test fix 

* Sort namespaces

This reverts commit 9da0bd76.

This has been causing friction when working on the FE.

* Generate conditional `describe` blocks

* Distinguish between premium features and enterprise artifact

---

This is the first step in series of commits that should allow us to test our feature flags in a more granular fashion.
We first need to remove the confusion around the words "enterprise" and "premium".

## Before
- `isEE` helper was used to mark setup with the premium token that has all feature-flags enabled.
- `isOSS` was used as the negation of the previous helper and as such wasn't strictly always true.
    - For example, isOSS would have resolved to true on enterprise instances without a token
This didn't backfire simply because we're running all EE instances with the token by default

## Now
There is a clear distinction between:
- OSS (literal open-source instance running on OSS artifract)
- EE (enterprise artifact without a token)
- PREMIUM (enterprise artifact with active premium token, with all feature flags enabled)