Revisions via new events system

update revision api tests so that they are focused on testing the endpoint functionality and not a bunch of other stuff.

flush out the unit tests for `(process-revision-event ...)` function which handles new events related to revision tracking.

rename to index to keep jekyll from barfing

Break up docs

fix placeholder on metadata field

handle subject to deal with sql backed cards

fixes #577

update readme to our current lack of a token on installation

add guide descriptions

fix filter widget height issue

Clean query fixes and other query builder inconsistencies

consistent auth scene

Remove dataset_query argument from runQuery so that it always cleans and runs the canonical version of the query (fixes issue with cleanQuery modifications not being persistent)

use inflection on table and relationships for object details

documentation and light refactor of <IconBorder> component

create an `:mb-run-mode` config property which defaults to "prod" and add couple predicate functions in our config ns for checking `is-prod?` and `is-test?`.  then update our event listener startup calls and wrap them with `(when (config/is-prod?) ...)` so that we only start them up when we intend to run the app for real.  lastly, update our environment for our expectations unit tests so that :mb-run-mode is "test" and thus our event processing listeners are not started for unit tests.