Upgraded to Rails 3.1.

Two changes to make the test pass:

* geocoder had an incompatibility with the new mysql adapter (probably)
* org.resources was picking up the newly added resource; we use
  org.resources.all to avoid it.

This upgrade doesn't take advantage of the asset pipeline, 3.1's biggest
feature. Patience....
Upgraded to Rails 3.1.

Specifically 3.1.4, to duplicate an earlier upgrade attempt.

Changes to make the tests pass:

* geocoder had an incompatibility with the new mysql adapter (probably)
* org.resources was picking up the newly added resource; we use
  org.resources.all to avoid it.
* Instantiate reassessment from scratch, because
  current_org.build_assessment deleted the existing assessment (!).
* When creating reassessment, explicitly split "look up answers for
  critical section" from "update them," because otherwise Rails tries
  to be clever and fails.
* Fixed Found bug - form_for should be evaluated in Rails 3.
* Pay for subscription again before checking for another re-assessment.

Conflicts:
	Gemfile
	Gemfile.lock
Upgraded to Rails 3.2.

Other upgraded gems (for compatibility):
acts-as-taggable-on, database_cleaner.

More on the database-cleaner error we encountered:
https://github.com/bmabey/database_cleaner/issues/98
Fixed edit/update payment action

Starting with Rails 3.1, form_for needs to be evaluated.

Also changed submit label to be more consistant
Fixed error handling when payment is not found

Need to return after redirecting to avoid double redirect/render
error.
Upgraded to Rails 3.2.latest

Upgraded for security reasons. Stay abreast of future updates to rails
3.2.
https://www.pivotaltracker.com/story/show/41917559