Update Oracle driver to have the `ssl` (boolean) option, with the expectation that any keystore/truststore params have been set as JVM parameters

Updating CircleCI config to allow for the following parameters to the `test-driver` orb:
- `extra-env`: a string that will be prepended to the `lein test` invocation, in order to set environment variables specifically for that test run.  Expected to look like `VAR_NAME=a VAR_NAME_2=b`. Defaults to blank (i.e. nothing).
- `test-selector`: a string that represents the Leiningen test [selectors](https://cljdoc.org/d/leiningen/leiningen/2.9.5/api/leiningen.test#test). Defaults to `:all` (i.e., run all tests).

Adding RDS root CA truststore file to our resources so that CircleCI (and anyone else, really) can refer to it

Defining new `be-tests-oracle-ssl-ee test-driver` task, and is identical to it except for the env vars required to connect via SSL instead (by specifying the RDS root CA trust store).  It only runs a few Oracle driver specific tests, not the full suite, since we are really only concerned with connectivity here.

Updating Oracle driver docs to discuss relevant JVM params and configuration

Turkish i, you won't strike again, hopefully

Merge 0.38.1 part 3: Merge #15005 into master

# Conflicts:
#	enterprise/frontend/test/metabase-enterprise/sandboxes/sandboxes.cy.spec.js
#	frontend/test/metabase-db/mysql/custom-column.cy.spec.js
#	frontend/test/metabase/scenarios/admin/datamodel/metadata.cy.spec.js
#	frontend/test/metabase/scenarios/admin/settings/localization.cy.spec.js
#	frontend/test/metabase/scenarios/dashboard/dashboard-drill.cy.spec.js
#	frontend/test/metabase/scenarios/dashboard/x-rays.cy.spec.js
#	frontend/test/metabase/scenarios/question/custom_column.cy.spec.js
#	frontend/test/metabase/scenarios/question/filter.cy.spec.js
#	frontend/test/metabase/scenarios/question/nested.cy.spec.js
#	frontend/test/metabase/scenarios/question/new.cy.spec.js
#	frontend/test/metabase/scenarios/question/notebook.cy.spec.js
#	frontend/test/metabase/scenarios/question/nulls.cy.spec.js
#	frontend/test/metabase/scenarios/visualizations/drillthroughs/chart_drill.cy.spec.js
#	frontend/test/metabase/scenarios/visualizations/drillthroughs/dash_drill.cy.spec.js
#	frontend/test/snapshot-creators/default.cy.snap.js

Merge 38.1 part 2 v2

Add test utility fn to find a free port, and call that from test-ssh-tunnel-reconnection-h2 instead of picking a random one

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

Merge x.38.1 part 1

0.39 improve custom expression

v0.38.0.1

the plugin raises an error on anything that looks like a hook (a
function that starts with "use") so am disabling eslint for two false
positives

Update Redshift driver to 2.0.0.3

Support controlling JDBC fetch size for Redshift

Adding `defaultRowFetchSize` parameter for JDBC URL in Redshift driver, which controls the `fetchSize` for all `PreparedStatement` instances created under it

Adding environment variable for controlling the new `redshift-fetch-size` parameter

Adding documentation for aforementioned new env var

Adding test for both the JDBC URL, as well as the `fetchSize` of the `PreparedStatement` itself

* Fix BigQuery not returning errors right away (#14918)

* Remove diacriticals and other invalid chars from BigQuery field alias identifiers

* Test fix

* Fix pivot table queries w/o data permissions

* Text fix 

* Refactor

* Ns sorting

* Custom expression completion: test that "case" is offered as a choice

* Remove Cypress alias

* Enable the test for arithmetic inside a filter

This is now working after the feature implementation (#14325)

* Use a better Cypress syntax

* Add some positive assertion

These new functions are to support MBQL's is-null and is-empty.