* Remove usages of dataset_query.type

* Remove more usages of dataset_query

* Introduce usesSegment and usesMetric methods on Question

* Fix type check

* Fix type

* Get query for UtilQuery

Fixes #19501

Redshift jdbc driver wraps intervals in a special class whereas postgres
simply returns strings. This unwraps the special redshift class into the
same string representation.

Fixes #25378

When using a relative filter with a starting from n units ago on an
aggregation with the same units, we were incorrectly assuming that we
would be working with a field ref at the top level. However, in this
scenario the field is nested such as `[:+ [:field $created_at
{:temporal-unit :month}] [:interval 1 :month]]`. This change makes sure
that we are altering the field-ref.

* Centering tab labels

* adding unit tests

* Switching to userEvent

* update `BulkActions` to new design

* incorporate PR feedback

* update `UndoListing` to match new design for bulk collection actions

* update e2e test to test undo flow

* incorporate PR feedback

* adding hover states, switching icons for buttons

* ChartSettingFieldsPicker unit tests

* fixing background hover state

* using userEvent.click instead of fireEvent

* adjusting e2e tests

* Conversion functions to and from pMBQL

* Appease Kondo

* WIP action data type tests

* DRY up the actions tests

* lots of type tests

* make the tests work

* reorganize tests

* WIP action data type tests

* DRY up the actions tests

* lots of type tests

* make the tests work

* reorganize tests

* reduce some flakes

* better time formatting in action forms

* sort out all the timezones 

* update after rebase

* rebase disaster

These previously passed around `Card`s, now they use `Question`.

The main changes are in `QueryBuilder`'s `handleSave`/`handleCreate`,
and `SaveQuestionModal`.

This also pulls a bunch of logic from `queries/utils/description` that
depends on the internals on `Question.datasetQuery().query` (ie. the
MBQL) into (mostly private) methods on `Question`. The tests for
`description` were moved into `Question.unit.spec.js`.

* move `BulkActionBar`'s styles to `BulkActionBar.styled`

* update `BulkActions` to new design

* update e2e test to not look for `bulk-action-bar` test id

* fix regex for finding `BulkActions` in e2e test

* fix bug where `BulkActions` was appearing then dismissing on page load

* incorporate PR feedback

* Refactor: Simplify code

* Fix custom field parameter lose their settings

Ref: https://github.com/metabase/metabase/issues/22788 this fixes the
issue where custom field parameter seems to be unselected when editing
dashboard a second time. The reason is because how current Metabase lib
is handling expression's MBQL. In FE, we uses `["expression", "name",
null] while in BE, we will normalize it to `["expression" "name"]`.

* update `BaseItemsTable` for new collections bulk actions ui

* use `getByLabelText` instead of `queryByLabelText` in unit test

* hide checkboxes from users without write permission

* update unit test to add cases for user with & without write permission

* fix `BaseItemsTable.styled` to dynamically set which columns to hide after breakpoint

* improve delete/update message for actions

Co-authored-by: Cal Herries <39073188+calherries@users.noreply.github.com>

* hide action parameter mappings on dashcards

* test DashCardCardParameterMapper

* use a better metadata mock

Co-authored-by: Cal Herries <39073188+calherries@users.noreply.github.com>

Previously, JS files isn't picked up by VS Code, so they'll have limited
intellisence. Also, Jest and Cypress has conflicting names e.g.
`describe` or `expect`. So, this commit attempt to resolve that as well.

* Ignore JS tests when doing CodeQL scans

* Do not run CodeQL scans unless needed

Adds --include-field-values flag to serdes v2 export command

* Use GitHub basic runners for `druid` and `sparksql` tests

* Reduce the `drivers` timeout to 45 mintues

* sort stacked tooltip rows

* update separator color