The issue was around our usage of `du/format-date` with a built-in
date format (`:date-hour-minute-second-ms`). Those Joda Time date
formatters don't default to the system timezone, which the code
assumed. Instead it defaults to UTC. We have code in the MySQL driver
that works around a MySQL driver bug by converting the date to a
string and then using the MySQL `convert_tz()` function. That code was
converting the date from the system timezone to the report timezone,
rather than UTC, which is what the Joda Time date formatter was
returning.

Fixes #8262

 Add a JoinQuery to `metabase.query-processor.interface`

Just adds a `:user` keypair with the current user information.

This will allow expressions in a join clause, rather than just a table name.

Mongo: correctly unpack nil dates

Fix issues with remappings and FKs with nested queries

Ensure that the new nested query FK tests don't run on drivers that
don't support both nested queries and FKs. Also needed to fixup
integer data types for Oracle and a nested order by issue for SQLServer

Mostly this change involves resolving the nested query, then using
that resolved nested query along with the top level breakout clause to
figure out if we need to add more fields to be projected from that
inner query.

The code previously was resolving that nested query but wasn't
resolving the breakouts after and reconciling that fields list. This
also adds some tests for these nested FK scenarios.

Import translations from POEditor

Don't create binned cards if the driver does not support binning

* Entity action instrumentation

* wrap trackAction in try/catch to be safe

* track events

* add top level entity actions category

Fix intermittent CI failures

Fix SSH tunnel details

Tag misc missing i18n strings

Add extra security headers to generic error message responses

Update `/pulse/test` to accept HybridCards

Don't fingerprint results when exporting data