Use CollectionMoveModal in query builder

Refactor LDAP/Email settings pages

Drag and drop collection actions + split up /api/collections/:id endpoint

Fix RecipientPicker not committing email address on input blur

Possible fix for "Cannot read property '_location' of null" CI errors

X-rays: parse query filters on the FE

Remove ComputationJob and ComputationJobResult models

X-rays: Correctly handle legacy `[:rows]` aggregation clause

X-rays: fix invalid queries in aggregate card with joins x-rays

X-rays: Don't use Druid metrics as breakout fields

The test query to ensure alerts aren't returned with pulse search, and
just filtering out the id of the pulse to ensure it's not in the
results. That test can fail if there happens to be a search result
with the same id as the (missing) pulse. Adding another predicate to
ensure it's only looking for pulses.

Anytime a new card/dashboard/pulse is created with a collection
position, or a card/dashboard/pulses has it's collection or collection
position updated, it's possible that other items in the collection
will need to have their collection position adjusted. This commit adds
a check to the PUT and POST routes of cards/dashboards/pulses to check
to see if the change impacts the position of other
cards/dashboards/pulses in the collection.

This also uses the same logic for the bulk card collection updates and
will adjust impacted cards as needed.

Add Gitter links

Rework xray candidates to use only 4 queries

Fixes various collections UI bugs and eliminates duplicate API calls

Search results should not include alerts

These were coming back with pulses, needed to include another query
clause to remove them.