[196-Disable] DB Migration
[196-Disable] Update agent index, controller, css, etc to show disabled state
[196-Disable] Update agent _form to include disable option
[196-Disable] Update agent diagram to show disabled state
[196-Disable] Cleanup agent show menu and include disabled state
[196-Disable] Make event index delete button red
Don't run things on disabled agents

Note: Pretty sure this works (limited manual testing), if you enable an agent again and run event propagation it will process all events while it was disabled. Not sure if this is a good thing or not.. May need some way to show them and potentially clear them?
Handle disabled agents properly in bulk_check
working on pushover agent.
Pushover Agent.
Pushover Agent.
Pushover Agent. Added ability to have a default message. Made some stylistic changes as well.
Pushover Agent. Added ability to have a default message. Made some stylistic changes as well.
no longer defaults api token or user key.
Add Jabber Agent
Merge commit 'b041a51ad11135ab1bcc9f5392730659861938a2' into 196-disable-agents

Conflicts:
	db/schema.rb
keep_event can be set to true to cause the incoming event to be re-emitted, with message merged in when present
add headers option to WebsiteAgent
Added pushbullet agent, refactored JSONPath merging

Moved the JSONPath merging into a concern because it is now used by
two agents, I also added Agent#received_event_without_error? which
is used by the hipchat and pushbullet agents.
Add non-intrusive support for AWS to Vagrantfile

This changeset adds support for AWS provisioning to
Vagrantfile. It won't get in the way of regular users
who want to just use Virtualbox.

The AWS provider will be required only if the user does:

vagrant up --provider=aws