config now ignores empty-string env vars

Make sure query templates containing newlines are parsed properly [ci drivers]

* apply @walterl's google auth fix
* remove :omit-source flag because it excludes mustache files and might have other effects

* apply @walterl's google auth fix

* remove :omit-source flag because it excludes mustache files and might have other effects

* Run status predicate for non-nil statuses only

* Specify defaults to log-info to avoid NPEs

Added a test to ensure that `log-info` doesn't throw an exception with
nil input.

- Differentiate between columns that record timezone info vs ones that are normalized. (i.e., TIMESTAMP WITH TIME ZONE vs. TIMESTAMP WITH LOCAL TIME ZONE in Oracle and other DBs that have this distinction.) Also differentiate between recording offset from UTC and Zone ID.

- New :type/Temporal base type for :type/Date, :type/Time, and :type/DateTime. Previously, :type/Date and :type/Time derived from :type/DateTime which didn't quite make sense.

- Add new attempted-murders dataset to count number of crows spotted. Has same temporal instant in a variety of formats with and without timezone to facilitate writing new tests

- New tests for TIME WITH TIME ZONE columns.

- Fix MySQL behavior for TIMESTAMP columns, which are the equivalent of Oracle TIMESTAMP WITH LOCAL TIME ZONE (i.e., they are normalized to UTC when stored) vs DATETIME (which are Local non-timezone-aware columns).

* copy over code from pr

* remove chronological

* remove tick formatting

* remove chronological

* use reporting_timezone

* remove unneeded tests

* remove import

* add timeseriesScale tests/fixes

* eslint

* more timeseriesScale tests

* remove now unneeded rangeFn

* more timeseriesScale tests

* report_timezone to actual_timezone

* display warning if timezones are mismatched

* extract getTimezone

* don't error if series doesn't have a card (in tests)

* move expected/actual timezones into data, add warning when series have different timezones

* fixes

* make sure getTimezone works on transformed series

* update actual/expected to results/requested

* call getTimezone from LAB renderer rather than apply axis

* include timezone as part of a timeseries interval

* missed variable

* include timezone when updating timeseries interval

* remove "report_timezone"

* add timezone fields to DatasetData flow type

* make the fields optional

* Fill data using timezone scale (#11143)

*  Make sure report timezone is taken into account when converting bucketed datetime filter clauses to ranges
*  Properly handle results for H2 and Oracle TIMESTAMP WITH TIME ZONE columns and SQL Server DATETIMEOFFSET columns
*  Enable timezone tests for all DBs; failing ones disabled for now

Test improvements: 

*  with-temporary-setting-values macro will now throw an Exception if passed an incorrect number of args in binding form
*  Rework Oracle test extensions to use Oracle's wacky INSERT ALL syntax to load all rows for a test dataset at once. Oracle tests 10x faster 
*  Rework timezone tests to be more idiomatic and readable
*  Test fixes to make sure various drivers can properly load test data with timezone-aware columns
*  A few fixes for test utility functions, including making sure the dataset macro works properly when used at the top-level of a test with multiple drivers
*  Fix the random Vertica test failures by adding retry logic when loading data fails
*  Other code cleanup

add an endpoint so that users who don't own a pulse can unsubscribe themselves from the pulse

* Don't fail entire query if we don't know how to convert result to literal

* Code cleanup 

The biggest performance improvement in history of Metabase since we switched to Clojure

Before when filtering by a "bucketed" datetime field we would wrap the field and the value(s) it was being compared against in casting/truncation functions. For example when compiling a query to find fields where month is September 2019, we previously generated SQL like this:

```sql
SELECT count(*)
FROM public.checkins
WHERE date_trunc('month', CAST(public.checkins.date AS timestamp)) 
    = CAST(timestamp '2019-09-01T00:00:00Z' AS date)
```

As mentioned in #4043, this is not good for performance! Metabase now generates logically equivalent SQL like

```sql
SELECT count(*)
FROM public.checkins 
WHERE (
    public.checkins.date >= timestamp '2019-09-01T00:00:00Z' AND
    public.checkins.date < timestamp '2019-10-01T00:00:00Z'
)
```

Fixes #4043
Fixes #11009 
Fixes #11010
Fixes #11011 
Fixes #11012
Fixes #11013

  

* Fix filtering by month-of-year and month in MongoDB; lots of new tests
[ci drivers]

* Test fixes  [ci drivers]

* Test fixes! [ci drivers]

Fix how optional field filter params are substituted; fix support for nested optional params (#10947)

* Param fixes [ci skip]

* Almost all working [ci skip]

* Test fixes

* Test fixes

* Test / linter fixes

* Fix linter errors

* [cmd] dump to h2 (#10843)

* Tests for load & dump commands

* Fixes

* test fixes

* Test fixes

* Test fixes

introduce a new permission parser to:

* handle permissions in a more declarative way
* allow permissions to be converted to a permission graph for databases without tables

fix bugs around setting data permissions for new database