* fix all user collection crumb spacing

* new browse link

* change label

* show regardless of pinned items

* homepage blocks

* table x-ray and reference links

* overworld db links

* minor copy changes

* move personal collections

* copy changes

* remove GSG from userland

* change default collection name

* more updates

* microcopy cleanup

* prettier

* fix colors

* fix typo

* rm overworld links

* lint

Previously this only allowed double values. If the average length
happened to be something like `13.0` some Javascript implementations
trim the `.0` and when the frontend POSTs the data, it includes `13`
instead. This was causing our schema validation to break as it was
looking for a `Double`.

This commit changes the schema to look for a positive numeric value,
not just a positive double which covers both cases.

This commit stores fingerprints and special type information for the
results of cards that have native queries, similar to what we store
for MBQL queries.

Google and LDAP users shouldn't be able to change their own email
addresses as we get that from the source.

Previously when an LDAP-based account was first created, the password
was encrypted and stored. Also the password was updated after each
successful LDAP login. This commit no longer does that and just stores
a randomly generated password (similar to what we do for Google auth).

Fixes #7635

To support this Cards now include fingerprints in the
result_metadata. That fingerprint is included in the query dictionary
and is available to the query pipeline. The expand/resolve/binning
middleware can make use of that fingerprint data to build the binned
query. Dimension options for these kinds of queries will also now be
available.

Note that binning is only available on questions that have result
metadata. If no result metadata (and thus no fingerprint) is
available, no dimensions options will be included and an exception
will be thrown if a binned query is attempted. In most cases, just
running a card once will populate that data.

Fixes #5938

The pulse GET responses include a PulseCard that isn't exactly a
PulseCard. It includes some extra information from the underlying card
useful for the FE to include in the display. When adding a card to an
existing pulse that has one or more cards already, the PUT include a
mixture of these HybridPulseCards (the existing cards for the pulse)
and CardRefs (for newly added cards). This commit changes the schema
to allow either and updates the tests accordingly.

This also adds similar flexibility to the POST so that it is
consistent with the PUT.

Fixes #7789

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.

Fixes various collections UI bugs and eliminates duplicate API calls

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

This is an issue resulting from the merge with the
collections-project-bulk-actions branch. A missing search string was
allowed in the form validation, but would fail as it tried to
lower-case the nil string.