* Store individual artifacts for each matrix combination

* Dummy setup

* Wait for the first job to finish

* Use volumes

* Use docker

* Run Cypress

* Initial setup

* Full upgrade test

* Try using maps in a matrix

* Fix breaking string

* Let all matrix workflows finish

* Update `matrix` naming

- `upgrade` is too specific.
- `version` gives us the flexibility to go in both directions (upgrade/downgrade)

* Rename the job to `cross-version-testing`

* DRY setup code

* Enable cross-version testing for EE edition

* Remove test retries

* Pass the secret to the Docker container

* Spice things up

* Schedule a job every Sunday at 9

* RIP namespace checker linter

* Remove linters.namespace-checker shim namespace

* Fix some small things

* Add Kondo to deps.edn to be able to debug custom hooks from REPL

* Fix macroexpansion hook for with-temp* without values

* Test config (WIP)

* More misc fixes

* Disable :inline-def for tests

* More misc fixes

* Fix $ids and mbql-query kondo hooks.

* Fix with-temporary-setting-values with namespaced symbols

* More misc fixes

* Fix the rest of the easy ones

* Fix hook for mt/dataset

* Horrible hack to work around https://github.com/clj-kondo/clj-kondo/issues/1773 . Custom linter for mbql-query macro

* Fix places calling mbql-query with a keyword table name

* Fix the last few errors in test/

* Fix errors in enterprise/test and shared/test

* Fix driver test errors

* Enable linters on CI

* Enable unresolved-namespace linter for tests

* Appease the namespace linter again

* Test fixes

* Enable clj-kondo for driver namespaces

* Fix CI command

* Fix CI config (?)

* Try hardcoding the driver directories in CI config

* Fix some busted stuff

* Enable the redundant fn wrapper linter

* Appease the namespace linter

* Bump shadow-cljs

This lets us use the template tag functionality

```
add experimental support for creating js template strings

used like str but emits native JS `` template

  (js-template "foo" (+ 1 2) "bar")

emits the literal

  `foo${(1 + 2)}bar`
```

But this required a few changes on our side as well.

Required for this:

-- LOGGING

Bumped glogi
```diff
   ;; new stuff
-  [lambdaisland/glogi "1.0.106"]]
-
+  [com.lambdaisland/glogi "1.1.144"]]
```
Annoying because it had a group name change due to Clojars policy. This
had the same error as us below. That's why I'm hopeful that it will
actually just work.

There were some changes with the Google Closure library with things not
included or referenceable. So I just removed these imports and the
typehints that used them. We'll need to verify that this still works but
both compiling for dev and release (with advanced compilation)
work. Still possible there will be some runtime errors but i'm hopeful
there wont be. We can grab a jar from CI and poke around

```shell
❯ npx shadow-cljs compile app
shadow-cljs - config: /Users/dan/projects/work/metabase/shadow-cljs.edn
shadow-cljs - connected to server
[:app] Compiling ...
[:app] Build completed. (100 files, 0 compiled, 0 warnings, 1.65s)

metabase on  nm-all-options-formatting [$!+?] via  v17.30 on 

  metabase-query took 2s
❯ npx shadow-cljs release app
shadow-cljs - config: /Users/dan/projects/work/metabase/shadow-cljs.edn
shadow-cljs - connected to server
[:app] Compiling ...
[:app] Build completed. (100 files, 30 compiled, 0 warnings, 28.04s)
```

```diff
             [lambdaisland.glogi.console :as glogi-console])
-  (:require-macros metabase.shared.util.log)
-  (:import goog.debug.Logger
-           goog.debug.Logger.Level))
+  (:require-macros metabase.shared.util.log))
```

```diff
@@ -37,4 +35,4 @@
 (defn is-loggable?
   "Part of the impl for [[metabase.shared.util.log/js-logp]] and [[metabase.shared.util.log/js-logf]]."
   [logger-name level]
-  (.isLoggable ^Logger (log/logger logger-name) ^Level (log/levels level)))
+  (.isLoggable (log/logger logger-name) (log/levels level)))
```

-- WARNINGS ABOUT shadowing `abs`

-  [medley "1.3.0"]
+  [medley "1.4.0"]

Similar to what we bumped for the backend. ClojureScript 1.11.x has an
`abs` function.

* use update-keys and update-vals in cljs

* bump clj-kondo in CI

Co-authored-by: dan sutton <dan@dpsutton.com>

Ignore documentation, markdown files, e2e files and backend tests.

* [CI] Conditionally run backend checks in GHA

Ignore documentation, markdown files and frontend tests.

* Fix indentation

* add dummy workflow clones to make originals required

* review

* fix percy flakiness

* run e2e

* fix percy flakiness

* update docs, remove timeout config that did not help

* Run mochawesome from within a custom Cypress runner

* Remove Mochawesome report from GitHub E2E workflows

* Removing old report configuration

* Adding mochawesome, mochawesome-merge and mochawesome-report-generator

* Adding mochawesome configuration to cypress.json

* Adding mochawesome context (screenshot and video) for failed runs

* Adding report to CI artifacts upon failure

* Fixing whitespace

* Fixing import pointed by es-lint

* Moving titleToFileName inside of failure analysis

* Adding suggestion

* Run the remaining E2E groups using GitHub Actions

* Remove Snowplow from CCI

* Remove waiting for databases from CCI

* Remove Cypress jobs from CCI

* Remove `fe-deps` from CCI

* Remove `tester` executor from CCI

* Remove all frontend-related from CCI

* Remove static viz bundle from CCI

* Remove E2E checksum from CCI

* Remove frontend checksum from CCI

* Trigger CI run #1

* Trigger CI run #2

* Trigger CI run #3

* Trigger CI run #4

* Trigger CI run #5

* Add Percy to the main E2E workflow

* Ignore unit tests

* Delete Percy workflow

* Do not run Percy tests on Cypress changes only

* Check whether visual regression tests should run at all

This reverts commit 8bf35e53.

* Do not run backend tests on unrelated changes

* Set explicit frontend test paths

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>

Co-authored-by: flamber <1447303+flamber@users.noreply.github.com>