A call to `rescan_values` launches a future but doesn't wait for it to
finish before checking that the function was called. We have no
guarantees when the future will run. This was causing transient test
failures, depending on when that future would run. This commit
switches from checking an atom to blocking on a promise. This insures
that the future would be ran (and function would be invoked).

This adds a new search route that provides a case insensitive query
across the name fields of cards, collections, dashboards, pulses,
segments and metrics. Users will only get search results for the
collections they are able to access.

* Entity pages (courtesy @kdoh)

* Add collection_id to Dashboards & Pulses (#7358)

* add search to top nav

* flip homepage, updated collections

* make recent views self contained, add to home

* recent items style, add some new colors

* adjust default text color

* add js colors to style guide

* add copy color

* segment loader

* move to landings

* landing nav

* segment list + loader

* clean up landing nav

* metric + segment listing

* mucking around with selectable stuff

* layout tweaks

* other loaders

* stronger left sidebar

* left sidebar

* fix landing

* layout port

* more tweaks

* nav tweaks

* explore

* collection wrap

* Add collection_id to Dashboards & Pulses

* GET /api/collection/:id default to returning everything. Wow!

* colleciton items loader

* dashboard move modal + cleanup

* currentCollection and items

* Add GET /api/collection/root endpoint

* pulse move modal

* MASSIVE ALERTS/PULSES/NOTIFICATIONS OVERHAUL

* move activity feed

* all items, cards

* link

* Filter out stuff you're not allowed to see from the so-called "Root" Collection

* Tests for GET /api/collection/root

* fix query builder and login layout

* lint + test fixes

* filter collection landing

* create dash modal

* new collection modal

* Tests for Dashboard + Collection permissions

* Tests for Pulse + Collection permissions

* Add new Pulse/Alert perms tests & lots of cleanup 

* Test fixes 

* tweak grid, add system to icon

* truncate long titles

* remove duplicate file

* add collection to create dashboard

* add collection selection to pulse edit

* icon spacing

* use site name for landing

* clean up routes

* include required pulse card keys

* fix entity menu action / link and add to collection landing

* update jest snapshots changed by icon

* use entity loader for collections

* use object loader for collection items

* fix colleciton edit and permissions

* remove unused file

* add key to collection grid items

* link to pulse edit

* use named list for collections

* Increase nav z-index Fixes #7523

* tweak z-index level

* fix filters

* fitViewport component and application

* add fitViewport to setup and post setup

* add root collection to dashboard move modal

* move to id for loading collections

* fix permission editor

* fix other instances of collection slug

* fix unit tests

* flow fixes

* dep flow fixes

* Fix admin routes not loading currentUser before checking auth

* Add id: root to Root Collection

* root collection items

* temporary archive links

* fix up question archive route

* redirect to collection on pulse creation

* use fitClasses on /explore

* Fix NavBar popover and modal interactions

* Fix comments about when migrations were added

* fix lint

* style updates

* fix recent views

* collection empty state

* Make FitViewPort more robust

* Fix side bar link states

* fix snapshot

* Fix alerts

* update link and landing nav style

* add archive collection route / modal

* add modal

* Disable onboarding integration test

* Fix disabling of dashbaord tests

* Update snapshots and lint error

* Fix collection archiving

* lint

* revert text color

* Reload collection list each time it's shown to ensure it's in the correct state:

* fix empty state image

* only show permissions edit option for the root collection

* nav

* simple layout

* fix grid

* grid component

* fix translation

* fitClassNames > fitClasses

* fix up collection items loader

* remove unused files

* remove type filter

* qb lives

* default to qb

* collection landing and components

* hoverable card

* placeholder search bar

* flip collection / content order on landing

* fix padding

* dashboards first in the list

* Merge master into collections-project

* only show sidebar if exists

* Add collection_position column to Card/Dashboard/Notification (#7675)

* add first version of pins

* Fix memory leak found using RedShift JDBC Metadata methods

Running sync calls several JDBC metadata methods that return
`ResultSet` objects. According to the JDBC spec, when the connection
associated to the JDBC ResultSet has been closed, it should free the
resources used by the ResultSets that were left open in that
connection. That doesn't look to be happening in RedShift. Closing the
ResutSet instance ourselves before the connection closes will ensure
that these resources are freed and doesn't allow the RedShift bug to
occur.

* use entity update instead of raw api

* Fix tests :wrench::unamused:

* Unified archive, search, schema data browsing, and refactor of entities

* Fix create dashboard modal

* Collections overworld (#7687)

* add overworld

* layout tweaks

* remove navbar browsing link

* table item cards

* search page layout and item icon colors

* search bar active style

* Remove Label & CardLabel models & endpoints

* DO NOT RUN TESTS ON SHUTDOWN! EVER!

* remove navbar browsing link

* table item cards

* search page layout and item icon colors

* search bar active style

* archive page changes

* Merge master into collections-project 

* activity style updates

* match search bar width to content

* schema grid

* greet with name

* type sync

* pin icon

* be round now

* search spacing and entitiy item last child border

* collection text color

* collection pinned item size / text

* better root collection name

* something styled

* init search empty state

* lint fix

* fix colleciton links. fixes #7716 (#7720)

* Merge master into collections-project 

* database card styling

* tweak hex value

* prettier

* fix overlap (#7737)

* Reload collections list in question save modal, and collections items list as stopgap until it's more automatic (#7731)

* Fix public question layout (#7732)

* Change Urls.collection() to take an ID, default to 'root', and use when creating pulse

* Collections project bg sync (#7740)

* default to bg-slate-extra-light color

* admin routes

* fix question archive redirect and archived message (#7730)

An incorrect query was written to pull the test-data DB that depending
on the order the tests were ran, would querying against a Druid DB
accidentally instead of the H2 db.

The previous code returned the result of the `db/insert!` this changes
that to user the same `fetch-user` function that is used elsewhere in
the user API to ensure we get the same data back (specifically looking
for `is_active`).

It's possible that database connections checked back into the pool
could still have session timezones associated with them. This can
cause the database timezone tests to failure. This will reset the
connection pool before the test runs to ensure that doesn't happen.

The goal is to make it easier to write tests with different data and
report timezone scenarios easier. The tests already have found issues
with our current code and their handling of these timezone
conversions. These tests exposed a bug in MySQL date support which is
also fixed in this commit.

Fixes #6554, fixes #6994, fixes #7393

This commit adds a new `*report-timezone*` dynamic var that should get
bound before dates get parsed (i.e. in a query pipeline
middleware). This allows an easier API `(->Timestamp my-date-string)`
while still ensuring the dates are interpretted correctly.

This is a step toward centralization of our timezone and date
conversion logic. As of this commit there are still separate/similar
logic for handling reporting timezone etc in Pulses, drivers etc.

Fixes #7584, fixes #6402

This test predates the move of min/max values of a field to
fingerprints. Rmoving this test as it's covered over there and doesn't
provide a lot of value in the fields sync code.

This commit adds a new "sync summary" message to sync/analyze/field
values scanning. It include information about how much data was
updated, begin/end timestamps around each phase etc.

Ensure the spected HTTP status code is included in
`metabase.query-processor-test.nested-queries-test` POSTs as when it
is not included our `retry` unauthenticated logic doesn't get
executed. Depending on the test order, the database and mock session
store might be out of sync and not retry authentication failures.

Fixes #7490