Previously this was done by checking if the FE had included
`:collection "some_table"` on the native query, but that's been
included for SQL queries lately, and broke "Explore Results".

Includes new e2e tests: one for this issue itself, and another
that the fix doesn't break real Mongo native queries.

Fixes #32121.

* 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.
```

[ci skip]

Co-authored-by: john-metabase <92878045+john-metabase@users.noreply.github.com>

This reverts commit 64707a89.

* 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]

Co-authored-by: Luis Paolini <paoliniluis@gmail.com>

[Manual backport] Accept US/Pacific timezone in Athena timestamp with timezone test (#31824) (#31834) (#31968)

Co-authored-by: Natalie <nat@metabase.com>

* Use BuildJet runner for `be-cloverage`

We're seeing OOM failures in `be-linter-cloverage` job in CI.

* revert back to using ubuntu-22.04 and increase heap size to 2GB

* 2gb to 4gb

* add comment

---------

Co-authored-by: Nemanja Glumac <31325167+nemanjaglumac@users.noreply.github.com>
Co-authored-by: Ngoc Khuat <qn.khuat@gmail.com>

Manual backport of #31605
Resolves #28792

Co-authored-by: metamben <103100869+metamben@users.noreply.github.com>

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

Co-authored-by: Jeff Bruemmer <jeff.bruemmer@gmail.com>

Manual backport of #31640

I forgot to do this in #31432.
As the result, some PRs have been stuck in CI due to the required check.

This PR will run the fallback job for `actions` E2E group when changed
files don't require E2E tests to run.

[ci skip]

We're trying to minimize the amount of hard coded IDs (or any other data) in E2E tests. This change doesn't assume admin's ID is always going to be 1. It fetches the id from the current user instead.

This should make test more resilient to change.

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

* fix the question description icon placement in the collection view (#31051)

* fix the question description icon placement in the collection view

* fix specs

* fix specs

* Backport changes from #31355
- Skip tests because the setup depends on refactoring done in master
- See discussion: https://metaboat.slack.com/archives/C505ZNNH4/p1686648256978279

* Remove unused code

* Fix sandbox table migrations for invalid perms table (#31508)

* fix migrations and add new test

* fix migration IDs in test

* dont fail migration if FK already exists

* rewrite without table aliases to try to fix error on mysql/mariadb

* try to rewrite again

* revert to prior version of query

* another attempt at a rewrite

* fix typo

* fix typo

* bump ci

* replace LIKE with =

* fix cherry pick conflict

Co-authored-by: Ariya Hidayat <ariya@metabase.com>

* enforce download perms on dashcards

* fix tests

Co-authored-by: Noah Moss <32746338+noahmoss@users.noreply.github.com>

* fix pivot table settings crash when the question is unaggregated (#31383)

* fix pivot table settings crash when the question is unaggregated

* error boundary

* fix spec

---------

Co-authored-by: Aleksandr Lesnenko <alxnddr@users.noreply.github.com>
Co-authored-by: Aleksandr Lesnenko <alxnddr@gmail.com>

We're seeing increasing number of timeouts in CI without any significant
changes in the test suite. This could be due to GitHub's runners performance.

[ci skip]

* Move core actions E2E tests to a separate folder

* Run new `actions` E2E group in CI

Metabase actions deserve their own E2E group, as the test suite around
them is expected to grow. This commit introduces `actions` E2E group to
the CI.

Updates Snowflake driver to decode uploaded private key file data if necessary

Co-authored-by: john-metabase <92878045+john-metabase@users.noreply.github.com>

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

* Fix native source query handling for mongo

* Add test for mongo nested native query

* Fix mongo `aggregation-at-index` usage

* Add test for source query with aggregation and sort

* Adjust test for presto and oracle

* Add PR suggestions

Co-authored-by: lbrdnk <lbrdnk@users.noreply.github.com>

Manual backport - Fix - Native editor buttons are incorrectly rendering on top of model metadata screen (#31142) (#31348)

* Manually backport #31142
- Replace createSampleDatabase with createMockDatabase
- Add missing metrics, schemas, and segments attributes in EntitiesState type
  - EntitiesState type has been heavily refactored in master and that version should be used
  - Tests will will crash without it these set in state.entities

* Fix types

* CI pre-release: Add sanity check (#31202)

* Pre-build the specific version and edition of MB (#31296)

Simply invoking `.bin/build.sh` will produce the uberjar without a
version. This is why @ariya created #30915 in the first place.

But the build script already takes `:version` and `:edition` arguments.
That is exactly what this PR is doing rather than manually unzipping the
uberjar in order to tweak its `version.properties` file.

---------

Co-authored-by: Ariya Hidayat <ariya@metabase.com>