This is to enable is-empty and non-empty tests on :type/MongoBSONID columns.

* hide filter sidebar button

* Unskip repro for #18021

* Simplify "recently viewed" test by visiting the table directly

* Do not hard code IDs

* Merge repro for #18021 with the related spec

* Better share embed widget disabled state

* Update embedding in other application copies

* Update test after embedding copy changes

* merge with better share embed state

* Address feedback: Add missing translation

* Address feedback: Split big component + fix misaligned option

* Fix normalize-token for mbql value clauses

* Fix formatting

* Add bug link to changes

* Change hour-of-day units to integers, not time with time zones

* Change display format of filter arguments to "h A"

* enable esbuild

* update i8n script and unit testing babel config

* split out babel loader for styled components

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-JSRSASIGN-2869122

* correctly handle multi inputs

* support more join operators in GUI query builder

* update style

* Make new color palette colors always hex
* Fix parameter order of series-setting
* Make pulse preview API endpoints honor viz-settings
Co-authored-by: Alexander Polyankin <alexander.polyankin@metabase.com>

* Add ddl persistence support for mysql

Since mysql does not have the concept of a (non-select) statement timeout,
it is necessary to use core.async to monitor the create table as select
statement manually. While mariadb does support a general statement
timeout, this will work for both vendors. There are some race conditions
here but in the context of persistence, this is ok. Mainly, the timeout
could hit right as the create table finishes. If that happens, the
statement will not be killed (because it was closed when finished), the
table will be created, but the function will throw a timeout exception.
In the context of persistence, this is ok since persisted-info will
remain inactive and the next refresh will drop the table and try again.

The other aspect to consider is that mysql doesn't rollback ddl changes.
So we have to manually keep track of what was done when testing the db
and undo the steps on failure. This isn't perfect, as the undo itself
could throw an exception, thus leaving the schema or test table in place,
that should only happen if a role has a create table but not a delete
table grant. In any event, if a our schema or test table sticks around,
they could be removed manually by a dba, or ignored without harm.

* Handle integrating mysql, and make sure exceptions are logged

* Add tests for execute-with-timeout

* Fix linters

* Switch to async/thread because reflection hints are lost by a/go and it's better not to do io in go-blocks

* Fix test