* fix broken test about resizing column by readonly user

* Update e2e/test/scenarios/question/saved.cy.spec.js

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

---------

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

so we need to account for that in serialization paths, storage
paths and when exporting/importing foreign keys

* more detailed question info

small styling updates

refine styling to match designs

update more e2e test

remove some changes

small styling updates

more question details

more question details

DateTime to typescript

test updates

type updates

export fix

fixes

* Icon Updates

* consolidate styles

* test updates

* address review comments

* remove more metabse settings

* fix missing update for latest version check

* test updates

* fix setting selectors

* cleanup data reference tooltips

* update test

* Unify FilterPickerForm

* Unify FilterPickerForm

* Add Select all in ListValuePicker

* Layout changes

* Layout changes

* Add tests

* Add tests

* Revert "Unify FilterPickerForm"

This reverts commit a7dfe884.

* Revert "Unify FilterPickerForm"

This reverts commit 8f002b87.

* remove the unknown premium feature warning

* remove ee-plugins from sdk

* remove ee-overrides from sdk

* Render values for temporal metrics

* Render data as rich

* Add tests for temporal metric

* Add TODO about isDate

* Check for errors in dataset

* Add unit test for timeseries dataset

* Add check for rows earlier

* Group tests better

* Add e2e test for metrics with no value

* Add test for metric with error

* Fix some minor collections issues

- explicitly provide access to the trash to all users, in the same way
we provide access to personal collections. Due to migration order, we
don't necessarily have a permissions row with the correct `perm_type`,
`perm_value`, and `collection_id` for the Trash collection. That's ok -
we don't actually move things to the Trash, so there isn't any
item where `collection_id=$trash.id` - but this may affect things like
effective ancestors for children of the trash. Let's be explicit about
the permissions that users have.

- replace a case where we manually calculated effective location and
then got the parent_id with just hydrating `:effective_parent`. This is
more efficient.

- replace the simple hydration method for `effective-location-path` with
a batched hydration method that fetches `visible-collection-ids` *once*
and then uses it to figure out the effective location path for each
collection passed.

This PR tests that the user can assign any of three cache invalidation strategies ("duration", "adaptive", and "don't cache") to dashboards and questions. The tests check that the following things are true:
* These strategies can be applied directly (via the sidebar)
* Dashboards and questions can inherit their caching strategy from the database that underlies them
* Dashboards and questions can inherit their caching strategy from the instance-wide default policy
* When a question inside a dashboard has been assigned a strategy, this is overridden by the strategy assigned to the dashboard.

What these tests do not examine:
* the schedule strategy
* the minimum query duration
* edge-case strategies, such as very long durations or very large values for the adaptive strategy multiplier

These may be addressed in follow-up work.

Closes #45355

* Alway render models and metrics links

* Remove useHasMetrics and useHasModels helpers'

* Update metrics test for metrics in sidebar

* Fix unit test

* Fix e2e tests

* fix static visualizations dashcard settings merging

* cleanup, fix types

* drop an empty file

Co-authored-by: Metabase bot <metabase-bot@metabase.com>

Fixes #47735

* Move stale endpoint to /ee/stale/${collection-id}

It's an enterprise-only endpoint, so it makes sense to put the whole
thing under enterprise.

* refactors ui to use ee stale endpoint

lint fixes, change endpoint location

fix failure e2e test

* Fix endpoint location

---------

Co-authored-by: Sloan Sparger <sloansparger@gmail.com>

* Don't encrypt `site-locale`

* Fix test for `site-locale`

The previous test required encryption. Theoretically the referenced
error just depends on the fact that something is logged during the
process of getting the value, so I reworked it to depend on that
directly rather than triggering it through an encryption key rotation.

* Add metric actions

* Fix dot menu width

* Refetch card when it's being (un-)bookmarked

* Add tests for metric dot menu

* Make sure bookmarked metric appears in sidebar

* Make sure restoring a metric works

* Add more tests for readonly users

* Use non-root collection for metric test

* Render Scalar metric values

* Add tooltip

* Render Scalar metric value using formatValue

* Move isMetricScalar and getMetricValue to utils

* Add e2e tests for scalar metric values

* Fix unit tests

* Add card query endpoint to metabase/api

* Use card query from api instead of question loader

* Add test for non-numeric scalar metric

* Move providesCardQueryTag to utils

* Use skipToken for query

* Clean up getDatasetScalarValueForMetric

* Add metric actions

* Fix dot menu width

* Refetch card when it's being (un-)bookmarked

* Add tests for metric dot menu

* Make sure bookmarked metric appears in sidebar

* Make sure restoring a metric works

* Add more tests for readonly users

* Use non-root collection for metric test

* show additional columns in the tooltip

* specs, tweaks

* drop stack dependency

* handle invalid columns

* change copy

Fixes #45938.

Remapping is handled at the top level of the query, and should be
ignored for inner queries. This PR hides it from `results_metadata` on
source queries.

It also fixes the interaction with `large-int-id` logic to make big
integers JS-safe.

* Question Settings Sidesheet (#47699)

Fixes #4755