This reverts commit 9b0e2817.

* .eslintrc -> .eslintrc.js

* This might work?

* add env for linting css modules class names

* avoid extending postcss-modules/recommended, specify just the used rule instead

* add missing . on comment

* Remove unused .detailName references

* Fix ManageApiKeys and GuiQueryEditor

* Fix SettingText and DashboardControls

* fix missing textUnspaced class

* remove usave of S.headerButton, that's actually never used because we never pass headerLink to ReferenceHeader

* Remove flexNoShrink

---------

Co-authored-by: Oisin Coveney <oisin@metabase.com>

* Add manual imports fixup

* Fixes

* Fixes

* Review fixes

* Review fixes

* Make Noah the codeowner for permissions et al

et al = `integrations` (OSS google auth, LDAP and Slack integrations) + `enterprise` (audit, advanced SSO, advanced config stuff).  `enterprise` also has LLM which doesn't really have a codeowner now, but it also doesn't need one.

* Correct the paths and the scopes

* Clarify that backport/no-backport is an internal thing

A few times per month, external contributors ask about the notion doc they can't access and about the labels they are not expected to set. This is not the experience we should give to people who not only take their time to contribute to metabase, but also actually read the PR template.

(slightly duplicated condition in the beginning and the end of the paragraph — "For those employed [...] If you're not employed [...]" — is on purpose)

* Add linebreaks in PR template

Co-authored-by: Tim Macdonald <tim@metabase.com>

---------

Co-authored-by: Tim Macdonald <tim@metabase.com>

* Upgrade node to 18.20

* Trigger CI

* Try 20 again

* Revert "Try 20 again"

This reverts commit 8f4b39e7a64f1fae7c60decfb91ea87aff81f587.

* Revert change

* Add nvmrc to the frontend_sources list

* SQL Lineage: Create the QueryField model

This links Cards (with native queries) to Fields, showing us which
queries use which Fields.

QueryFields are automatically maintained as part of the Card lifecycle

Cards with stale queries (powered by QueryField info) are exposed via the `card?f=stale` API

* specify GH project board per team

* update teams projectUrls

* remove QC team project url

* notify slack on cross-version test failure

* update name

* Fixing E2E Cross-version Tests

E2E cross version tests were broken for multiple reasons, primarily due to changes made in UI layout, cypress testing, and data changes. Overall, the basic workflows still work, but subtle click order differences and other small changes made the entire job consistently fail.

To fix this, this PR:
- Provides a function, `parseVersionString`, which computes version information provided a test version string. This information includes the raw string version, the edition (ee or oss), and the major, minor, and patch version of the version string.
- In the same file, `cross-version-helpers.js`, adds constants identifying versions in which certain breaking UI or Cypress changes occurred.
- Finally, a set of exported functions are provided which take a version object and execute conditional logic based on the provided version so that behavior is consistent across Metabase versions.

The versions are computed in `cross-version-source-helpers.js` and `cross-version-target-helpers.js` and are used in js files as shown:

```js
import { visualize } from "e2e/support/helpers";
import {
  fillAreaUnderLineChart,
  newQuestion,
  saveQuestion,
} from "e2e/test/scenarios/cross-version/helpers/cross-version-helpers.js";
```

This then allows logic like the below, where the high level call is made and the right logic is dispatched based on the version information.

```js
it("should create questions", () => {
  cy.signInAsAdmin();

  cy.visit("/question/new");

  newQuestion(version);

  // eslint-disable-next-line no-unscoped-text-selectors -- deprecated usage
  cy.findByText("Orders").click();
})
```

Other smaller changes were also made that created a more universal sequence of UI actions.

Fixes #39229

* clear -> click

* Fixing area icon selection

* Restoring scheduling to align with master

* fe lint

This PR narrows down the matching pattern for the milestone reminder to
only the descriptions that explicitly contain one of the closing keywords
followed by the issue (number).

To verify that the proposed solution works, please check:
- https://regexr.com/7sk94

Also see the list of the closing keywords as defined by GitHub.
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests



* Make the pattern case insensitive

Co-authored-by: Nicolò Pretto <info@npretto.com>

Remove note

Resolves #38301

* Upgrade `actions/download-artifact` action to v4

* Upgrade `actions/upload-artifact` action to v4

* Add path filtering for cljs workflow

* Add shadow-cljs.edn to cljs file paths

Co-authored-by: Vladimir Zaytsev <vladimir@trunk.io>

* Add Unit Test Stress Test Flake Fix workflow

* Add "frontend" prefix to the workflow to disambiguate between backend and frontend

* Revert "Fix trailing whitespace (#38057)"

This reverts commit 1de0326c.

* Revert "Add upload test results to Trunk (#37490)"

This reverts commit a36347a1.