Major Mac App Improvements

FIX: X-raying druid timestamps [WIP]

Be less clever

Improve Elastic Beanstalk VPC docs

Adding a note about restrictions on subnets that apply to ELB and RDS, slightly more nuanced than "just check all the boxes". See http://discourse.metabase.com/t/cannot-setup-on-aws-in-vpc/2166 for more detail.

update copy to reflect no limit to number of pulses

Fix new question flow test transient failure

Fix bug with card database_ids nog being populated on native queries

Added timestamp formatting for druid select queries [ci drivers]

Druid select queries don't allow setting of a timezone. This commit
will parse the timestamps coming out of Druid and reformat them using
the user's report timezone or system timezone. This allows Druid
select queries to have similar timezone semantics to other supported
databases.

Fixes #3690

This utility function temporarily changes the JVM's timezone to
something different and puts it back after the body of the form is
invoked. Moving it to metabase.test.util so other tests can use it.

Switch from the PostgreSQL driver to Redshift [ci drivers]

The pre-update function was returning nil for their values which was
then getting stored. This commit does not switch
REPORT_CARD.DATABASE_ID to NOT NULL, that's written up as #5999.

Fixes #5998

Fix word mistakes in docs.

Pull Release 0.26.1 back in

Redshift JDBC connection URLs can be writtend with the postgresql
subprotocol or the redshift protocol. This can cause problems as the
DriverManager (depending on how the classes have been loaded) will be
the first matching driver for a subprotocol. We could get the Redshift
driver when we were intending to get the PostgreSQL driver. Adding
this flag will ensure that we don't inadvertantly get the Redshift
driver when we intended to get PostgreSQL driver.

Calling metabase.test.data/id with no args ensured the db was created,
I added that same check to the other arities of the id method.

Fixes #5424

Fix performance problems where xray visualizations were rerendered unnecessarily

Reverse the order of dropping the async xray tables

On MySQL dropping the computation_job table first violates the FK
constraints. This commit just flips the order of deletes. It also adds
a new validCheckSum to ensure users that ran the previous version fo
the migration will still work.

Fixes #6050

* add preview banner

* add icon / survey link

Try to fix transient CI failures in ObjectDetail.integ.spec.js