* auto cherry pick to release branch on merge into master

* rename workflow, label

* Enable clj-kondo failures on missing docstring; remove bikeshed

* Add missing docstrings

Some front-end tasks require Shadow CLJS to compile files into
JavaScript, therefore let's cache the JARs which it needs.

There's no `--lockfile` option, the valid one is `--frozen-lockfile`.

https://classic.yarnpkg.com/en/docs/cli/install/#toc-yarn-install-frozen-lockfile

* Move smoke tests to the CircleCi

Closes #16741.

* Remove smoketest script

Signify this is for internal use for the Metabase team, and remove ETA from the template (since that's tracked outside of GitHub).

- Cherry picks 274be949 from `master`, which extracted unit and timezone tests from CircleCi and made them run using GitHub actions
- Synchronizes the "state" between the `master` and `release-x.39.x` branches

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

* Port code for building i18n resources to Clojure build scripts; remove dep on gettext

* Use Metabase classloader

* Test fixes 



* Bump adoptopenjdk version

* Delete gettext dependency from Dockerfile

* Update developers-guide.md

* Address PR feedback

* Fix frontend singular msgstr format

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

* CI: Run clj-kondo linter

* Add some more paths

This was duplicated with the "feature or project implementation" template.

* Shared CLJ/CLJS lib (PoC/WIP)

* PoC 2.0

* Fixes 

* More test fixes 

* Bump shadow-cljs version

* Fix more stuff

* Need to ^:export the exports

* CI fixes 

* Add eslintignore

* Ignore cljs files for FE code coverage

* Try prefixing CLJS -> JS import with goog:

* Revert indentation change

* No goog:

* Add .prettierignore

* Use advanced build for now for JS tests unit we can figure out how to make it work

* yarn remove flow-bin eslint-plugin-flowtype

* CI: remove fe-linter-flow

* Remove Flow from ESLint config

* Remove Flow type annotations and directives

* Simplify Flow types for React elements and components

* Import missing Flow types

* Remove lint-flow from package.json

* Use GitHub Actions to check for Dockerfile correctness

* Wait for the health check API endpoint

Users should follow instructions in our SECURITY.md file instead.

Flesh out changes to simplify, and add 'how to test this feature out' section.

* Use GitHub Actions to run front-end linters

* Add docs/, needed for lint-docs-links

* No need to honor ci skip since the execution is path-conditional already

* Remove front-end linters from Circle CI

* package.lock, in case any npm/run scripts changed

Co-authored-by: Tim Macdonald <tsmacdonald@gmail.com>

https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning

This completes one step towards removing Enzyme.
The complete list of all tests is at #13657.

* Run each test in isolation

* Convert `EditUserModal.integ.spec.js` to Cypress

* Convert `PeopleListingApp.integ.spec.js` to Cypress

* Convert `GroupDetailApp.integ.spec.js` to Cypress

* Delete `GroupsListingApp.integ.spec.js`

It was already covered in Cypress.

* Delete `NewUserModal.integ.spec.js`

It was already covered in Cypress.

* Convert `UserActivationModal.integ.spec.js`

* Convert `UserPasswordResetModal.integ.spec.js`

* Convert `UserSettings.integ.spec.js`

* Remove integration tests

* Remove integration tests from CI

* Fix linter errors

* Delete `AuditTable.integ.spec.jsx`

* Clean up `people.cy.spec.js`

* Update assertion that makes sure XHR didn't happen

* Remove redundant command from PR template

Note: `yarn-lint` already runs `yarn flow`.
https://github.com/metabase/metabase/pull/14174#discussion_r549790198

* Remove explicit mention of timezones in `developers-guide.md`

To simulate a regular end user (with just JRE, not JDK), the launch is
varied across different Java versions.

Since Metabase doesn't work with Java 15 yet, it is explicitly marked as
a known issue (without marking the whole build as a failure, thanks to
`continue-on-error` flag).

* Collapse the build commands
* Set the env var INTERACTIVE to false
* Group dependency and build steps properly
* Add more paths to ignore

Added a feature implementation issue template

* needs triage label to simplify triage

* cause obviously this is how multiple labels should be specified