Adding rake task for synching payment data with the crowtilt api

When a campaign tilts (hits its goal), the crowdtilt api automatically charges everyone's card in the background.  Successful charges become status 'charged', while unsuccessful charges become status 'rejected'.  Rejected payments usually occur due to long-running campaigns, in which initial card authorizations have a chance to expire before the campaign hits its goal.

One issue with Crowdhoster is that the payment information that is stored locally on the app is not updated when the  Crowdtilt API performs the bulk set of transactions in the background.

This rake task is a first step toward keeping the data better in sync.  After a campaign tilts, this rake task can be run to individually update each local payment record with the corresponding data from the crowdtilt API.  This will allow the site owner to clearly see which cards were successfully "charged" and which were "rejected"