* Try sleep

* Use db.setup/migrate! directly

* Use v47.00-001 in test description

Co-authored-by: Ngoc Khuat <qn.khuat@gmail.com>

* Add comment explaining why

---------

Co-authored-by: Ngoc Khuat <qn.khuat@gmail.com>

* keep standalone values when collapsing column

* adjusting unit test

* PR Feedback

* adding space

* removing only

* Adjusting behavior and tests

* adjusting data_grid unit tests

* move component files into directories

* fix tests

* improve `ColorRangePopover` ux

* add unit test

* improve test

* improve test

* Updating to cypress 12

* updating deps

* Updating Tests. Be Green Plz

* removing custom test id from select button

* Select Button Tuning

* Move `QuestionRowCount` to its own directory

* Run small cleanup

* Convert to TypeScript

* Add row count display tests

* Simplify `QuestionRowCount`

* Test changing the limit

* Test can't edit limit when needed

* Simplify `QuestionRowCount`, semantic HTML

* Extract styled components

* Fix static label's font-weight

* (db/transaction body) -> (t2/with-transaction [_conn] body)

* (db/with-call-counting) -> (t2/with-call-count)

* db/execute -> t2/query-one

* Avoid updating tiny-db in ssh test

* Avoid updating sample-database during testing

* Fix write test

* Separate date from datetime binning options

The BE sends over binning indexes for each field and a top level map for
how to interpret these keys.

```javascript
❯ http get http://localhost:3000/api/table/10658/query_metadata Cookie:$SESSION -pb
{
    "active": true,
    "caveats": null,
    "created_at": "2023-03-21T22:20:42.363169Z",
    "db": {
        "engine": "postgres",
        "features": [ "full-join", ... ],
        "id": 499,
        ...
    },
    "db_id": 499,
    "dimension_options": {
        "0": { "mbql": [ "field", null, { "temporal-unit": "day" } ],
               "name": "Day",
               "type": "type/Date"},
        "1": { "mbql": [ "field", null, { "temporal-unit": "week" } ],
               "name": "Week",
               "type": "type/Date" },
        "10": { "mbql": ["field", null, { "temporal-unit": "quarter-of-year"}],
                "name": "Quarter of Year",
                "type": "type/Date" },
        "11": { "mbql": [ "field", null, { "temporal-unit": "minute" } ],
                "name": "Minute",
                "type": "type/DateTime"},
        "12": { "mbql": [ "field", null, { "temporal-unit": "hour"}],
                "name": "Hour",
                "type": "type/DateTime"},
        ... // more options. They have a type, an id, and an mbql clause
    },
    "display_name": "Different Times",
    "entity_type": null,
    "fields": [{"name": "id",},
               {"name": "dt",
                "dimension_options": [
                    "11", "12", "13", "14", "15", "16", "17",
                    "18", "19", "20", "21", "22", "23", "24", "25"]
                "database_type": "timestamp",
                "effective_type": "type/DateTime",
               },
               {"name": "t",
                "dimension_options": [ "26", "27", "28" ],
                "effective_type": "type/Time",
                "database_type": "time"
               },
               {"name": "d",
                "database_type": "date",
                "dimension_options": [ "0", "1", "2", "3", "4", "5",
                                       "6", "7", "8", "9", "10" ],
                "effective_type": "type/Date",
        }
    ],
    "name": "different_times",
    ...
}
```

This PR adds some new types just for dates so that you don't get offered
by group a date by hour or minute.

This adds new indexes to this list, which makes us wary that these
indexes have leaked out and cannot be changed. But that is not the
case. This is essentially compression on the response. When the FE saves
a query, it does not include the index but uses the mbql query to insert
the proper temporal-unit:

```clojure
;; a "date" field choosing the quarter option
{:type :query,
 :query {:source-table 5,
         :breakout [[:field 49 {:temporal-unit :quarter}]],
         :aggregation [[:count]]},
 :database 1}

;; the same query but binning by week
{:database 1,
 :query {:source-table 5,
         :breakout [[:field 49 {:temporal-unit :week}]],
         :aggregation [[:count]]},
 :type :query}
```

So the index is relative to just the editing session of the query, and
the indexes do not have to be stable when we add new ones.

* athena and mongo (others?) don't have a date type

the test expects a date field to have date binning options. previous, we
made no distinction for binning options for date vs datetime fields. Now
we do and have to manage expectations in the tests.

* mongo returns type/Instant

* fix pie chart legend not fading on hover

* use `aria-current` in test instead of directly checking style

* fix failing test

* db/count -> t2/count

* db/exists -> t2/exists

This is tested implicitly by round-tripping every legacy MBQL query
the BE tests pass to `mt/mbql-query` etc.

* Use type/JSON instead of type/SerializedJSON

* Tidy migration

* Update migration

* Fix rollback migration for h2

* whitespace

* Add test for migration

* Fix test

* Add rollback

* whitespace

* Test JSONB type as well as JSON

* Don't fingerprint JSON columns

* Remove comment, that might be wrong in the future

* Update test

* Add tests for fingerprinting

* Use base-type JSON for fingerprinting base query

* Add test for visibility-type=details-only

* undo .

* Change migration id

* Fix migration test

* Merge master

* Exclude mariadb from tests

* Make is-mariadb? public

* convert db\/insert! to t2

* Drop support for nested field columns for redshift

* db/select -> t2/select

* Remove clj_kondo file

* Add action.dataset_query to search results

* Add action.database_id to search results

* Unskip repro

* better FE error handling for action query display

* update repro

---------

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

* Remove usages of `cy.addFilterToDashboard` custom command

* Fully remove `cy.addFilterToDashboard` custom command

They were getting deleted, but only when granting permissions.

Now they will be deleted whenever their v1 path counterpart gets deleted.

* WIP improvement of recent_views endpoint query

* Adjust query to actually include models (cards with :dataset true)

This was not part of the recent_views before, so I think it's actually an improvement to the feature as well as
improvement to the characteristics of the query itself.

* Linter fixes

* One more take on recent_views query. Last 30 days, all req's in 1 query

This query combines view_log and query_execution
Keep query_executions when they are card with context 'question'
Keep any card views when they are 'datasets' (aka models)
Remove duplicates with GROUP BY model, model_id
Sort by timestamp desceneding
Remove any views that are bookmarked by using NOT IN

* An improved query that handles all logic in one db query

* Adjust limit in case archived cards/dashboards are in the list

* Make fn private for linter

* Add one additional constraint to prevent pinned items from counting as viewed

* Address review feedback

* Accidentally slipped this in... not needed on this PR

* fix color range for null values in table

* add another test case

* initial changes

* styling change

* address comments

* fix sso settings

* update test

* update test

* remove warning

* fix test