set the :model to "install" when doing :install activity.  set the :model_id to the `user_id` on :user-joined activity entries.  and make the proces-activity-event public so that we can use it for testing easily.

include a :card-create event in our view logging because realistically the user is always looking at the card they are creating.

when recording a database-sync activity set the database_id value as well as the model_id value for the activity.

do a little cleanup work on our event processors to make them more robust and fix a small bug in the event tracking for database sync.

adding in the new view tracking code so that we can have an accurate Recents section on the homepage (implements #938)

get all of the card filtering by Table stuff working.  formatting is pretty close now on Saved Questions tab.

do a quick reshuffling of the events lifecycle functions so that we can make it easy to spin up new event listeners for different things, including our second listener which will be for view count tracking.

finish off card activity handling by adding in ability to track the database & table associated with an activity item.

be consistent about using :custom_id instead of :tracking-hash or other ways of specifying an activity custom identifier.

update the database sync event publication so that we can actually track start & end as separate events but part of the same activity.  to do so we add a :tracking-hash to the events when they are published which is meant to remain consistent throughout the sync, then we implement our activity tracking code so that we can lookup an existing activity item and update it based on the custom hash.

publish and :install event and listen for it in our activity feed so that we can create the first entry.  also, implement user login event handling so that we can identify when a user logs in for the first time and we can publish an activity feed entry for :user-joined.

streamlining more of the event bus and activity stuff and rounding things out.  adding new migration which creates the `activity` table.

rounding out a few things.  now have all persistent functions for cards & dashboards publishing activity events.

add some additional api validation so that we ensure the caller passes in an `id` param if they specify a filter mode of :database of :table

ability to filter list of Cards returned from GET /api/card by `:table` or `:database` both of which require a second arguement for `id`

make sure that new card attributes extracted from query dictionary are always set automatically on pre-update and pre-insert and tidy up unit tests to make sure everything is passing.