Inactivate sponsorship

PT story https://www.pivotaltracker.com/story/show/79590362

- replace deletion of sponsorship with setting `.active = false`
- modify sponsor view to show inactive sponsorships separately from current ones
- remove unnecessary routes & use ActiveAdmin `member_action` for inactivation (thanks, @sampritipanda!)
- ensure that actively sponsored orphans cannot be re-sponsored
- ensure that sponsorship inactivation correctly re-enables sponsoring of the same orphan
Right. This line of code is correct as written because it calls the `.active` method on an instance (i.e. accesses the attribute). But it might be a good idea to rename the scope so that such calls are clear without checking whether they are made on an instance or class. Any suggestions? Current & former