update gems-status to 1.76
add the number of security alerts
show status even if the security alert is pending
show status even if the security alert is pending (2)

In the previous commit I forgot the edit view
remove previous gems from a ruby_application

Fixes #14
Fixes #6
merge ignore and refuse status into just ignore

Fixes #13
the previous commit broke something I am fixing here

Removing all the rubygems from an application broke the relation with
the security alerts, making old security alerts reapear since the status
was "Pending" as in new security alerts.

This fixes it by looking for security alerts but without the restriction
of belonging to a particular gem, and updating those security alerts in
case they exist with the gem relation.
add db migrate into travis
fix: looking for security alerts by sec_key was not working
update schema
Merge branch 'master' into heroku

* master:
  update schema
  fix: looking for security alerts by sec_key was not working
  add db migrate into travis
  the previous commit broke something I am fixing here
  merge ignore and refuse status into just ignore
  remove previous gems from a ruby_application
  show status even if the security alert is pending (2)
  show status even if the security alert is pending
  add the number of security alerts
  update gems-status to 1.76

Conflicts:
	.travis.yml
	Gemfile.lock
	app/views/security_alerts/edit.html.erb
	app/views/security_alerts/show.html.erb
	db/schema.rb