Add new flag for BigQuery to use JVM timezone [ci drivers]

Merge branch 'bigquery-using-jvm-timezone' of github.com:metabase/metabase into bigquery-using-jvm-timezone

core.async take/put ops in go blocks use single ! functions

This commit adds a flag to allow dates parsed from BigQuery to be
parsed in the JVM's timezone rather than UTC. By default all BigQuery
dates are in UTC but it's possible to modify the timezone via a
function invocation. This flag allows installs that have all of their
queries modifying the timezone in that way to match the actual and
expected timezones via setting the JVM's timezone.

When using the core async `alts` and `>` functions, they should use
the single `!` version (i.e. `alts!` and `>!` instead of the `!!`
version. When using HTTP/2 and a reverse proxy, the multiplexed HTTP/2
requests get issues to Metabase not as a single connection, but as
multiple requests at the same time. The combination of those
simultaneous requests and the incorrect usage of the `core.async`
functions leads to the query responses not being delivered.

Fixes #8312

Fix an issue retrying migration failures

The existing code would retry a database migration if it failed. If
the failure was such that it didn't release the lock, the retry will
always fail. To make this worse, if the user didn't have Metabase set
to the WARN log level, they would not see the original exception, but
only the lock exception.

This commit tries to release the lock if a failure occurs. This will
cause the real exception to bubble up on subsequent retries rather
than complaining about the lock.

Ensure we handle no git Metadata for BQ startup

When connecting to a Google service, we identify ourselves with a
string that includes version, hash and branch information. If a user
downloads a Metabase tarball from Github, it won't have that Git
metadata and we will throw a NullPointerException on startup.

This commit just ensures we always have a value for that string, even
when there is no git metadata available.

Fixes #8368

Fix FK remappings with a user included fields clause

Our existing remappings code didn't work when an MBQL fields clause is
present. Typically that fields clause is populated by the
`add-implicit` middleware, but that doesn't happens with the user
included fields.

Fixes #8270

* show pinning message to admins

* microcopy tweak

* localStorage isn't async

* add AdminPinMessage tests

Translations (v0.30.1)

Fix template tags reordering while editing

Use nils in datetime fingerprint as placeholders when all values are nil

Respect :active flag in related and xrays

Don't needlessly re-sort results

Use map display to compare states and countries

xrays: Ensure stable series ordering

* tweak download widget

* add updated icons

* hover inherit util + download hover state

Shorter x-ray action labels

Add missing Redshift driver password field