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)

* fix heading input clipping

* fix hover padding when hovering over resize handle

* refactor CSS module to styled component wrapper

- move all CSS logic into one file

* refactor to use theme breakpoints

* move single row styling to ReactMarkdownStyleWrapper

* change padding only for single row text cards

* fix text card clipping

- adjust padding size based on breakpoints (proxy for grid row height)
- adjust font size based on breakpoints
- set styles based on grid mobile/desktop layout

* refactor css colors

* do not apply filter values to text cards in edit mode

* adjust font-size for open sidebar

* refactor font-size adjustment

- move font-size adjustment into TextCardWrapper so
  - styles are applied in edit and saved mode
  - styles are applied to textarea as well as markdown preview

* fix type error

* fix text offset for markdown preview and textarea

Fixes #32081.

Fixes #32058.

The previous setting accidentally executed a scheduled job **every minute**
on Sunday, when we actually wanted it to run only once on that day.

This PR fixes it and it will now run at 10PM every Sunday.
https://crontab.guru/#0_22_*_*_0

[ci skip]

* moving dashboard events 1-0-2 to 1-1-2

* update version number

---------

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

* update row chart measuring function

* add test to check if the line chart retnders

* Fix Docker `latest` tag logic in the release workflow

As noted in #32036, the current logic doesn't account for the existence
of the N+1 RC tag when the current release is N. In other words, it
didn't promote `v1.46.6` to the latest Docker tag because it included
`v1.47.0-RC1` in the list of the relevant tags it compares against.

This PR fixes that and closes #32036.

**Before:**
```
Current version for v1.46.6 is {
  prefix: 'v1',
  feature: 46,
  maintenance: 6,
  build: NaN,
  isOSS: false,
  isEE: true,
  prerelease: false
}

Enumerating all git tag...
Found total 414 tags

Filtering for EE
Found total 116 filtered tags

Sorting tags to find the highest version numbers...
Showing 20 tags with the highest versions...
     v1.47.0-RC1
     v1.47.0-RC2
---> v1.46.6
     v1.46.5
     v1.46.4
     v1.46.3
     v1.46.2
     v1.46.1
     v1.46.0
     v1.46.0-RC1
     v1.46.0-RC2
     v1.46.0-RC3
     v1.46.0-RC4
     v1.45.4
     v1.45.3.1
     v1.45.3
     v1.45.2.1
     v1.45.2
     v1.45.1
     v1.45.0

The latest container image stays as v1.47.0-RC1
There is no need to tag the v1.46.6 container image as latest.
```

**After the fix:**
```
Current version for v1.46.6 is {
  prefix: 'v1',
  feature: 46,
  maintenance: 6,
  build: NaN,
  isOSS: false,
  isEE: true,
  prerelease: false
}

Enumerating all git tags...
Found total 430 tags

Filtering for EE which excludes prerelease tags...
Found total 94 filtered tags

Sorting tags to find the highest version numbers...
Showing 20 tags with the highest versions...
---> v1.46.6
     v1.46.5
     v1.46.4
     v1.46.3
     v1.46.2
     v1.46.1
     v1.46.0
     v1.45.4
     v1.45.3.1
     v1.45.3
     v1.45.2
     v1.45.1
     v1.45.0
     v1.44.7
     v1.44.6.1
     v1.44.6
     v1.44.5
     v1.44.4
     v1.44.3
     v1.44.2

Thus, the container image for v1.46.6 must be marked as latest.
```

* Remove unnecessary whitespace

[ci skip]

* Cljs/TS wrapper for join fields should handle :all and :none (#32006)

* Split metadata into separate expected-columns method

* MLv2 `joinable-columns`

* Cleanup of options

* Opaque join strategy

* Opaque join strategies, part 2

* MLv2 table-or-card-metadata

* Fix `join-fields` schema while we're at it

* Fix cljs test

* Remove conditional-in-conditional

* Cleanup

* add titile to unsub

* fix spacing

* Fix TextWidget inconsistent behavior when all chars are removed

* Revert "Fix TextWidget inconsistent behavior when all chars are removed"

This reverts commit d17b530ab0d85b7d1fde5dc0566ebf0641bd5a46.

* Add normalization for value in field filters

* Add normalization for default value

* Update frontend/src/metabase/query_builder/components/template_tags/TagEditorParam.jsx

Co-authored-by: Mahatthana (Kelvin) Nomsawadi <me@bboykelvin.dev>

* Add e2e test

---------

Co-authored-by: Mahatthana (Kelvin) Nomsawadi <me@bboykelvin.dev>

* Convert `NotebookCell` to TS, add `forwardRef`

* Move styled components to a styled file

Fix - Adding filter of summarized field grouped by latitude and longitude on a map causes table visualization error (#31952)

* Fix #30058

* Add missing setting key

* Add a unit test attempt at #30058

* Mock store instead of using deprecated MetabaseSettings.set

* Remove LeafletGridHeatMap unit tests

* Add e2e test for #30058

* Fix typing

* Don't allow undefined "map-tile-server-url"

* Tag the test with repo and issue id

Replay is adding a significant overhead and is making every single run
fail. This is messing with our statistics and analytics.

While the Replay.io team is working on some optimizations that would
remove the overhead, we can significantly dial down the frequency of
these runs. We'll switch to running them only once per week, on Sunday.

For now...

Debian Bookworm has Java 17 as the default and Java 11 has lots of steps to install. Going back to Bullseye with Node 18