defer clr contribs

[owocki]

Description

the guys at status have forgotten their private key to the nimbus grant they have up.
i went back and forth with them about what to do… and heres the solution we landed upon:
i think we should open up a new grant, hide the old grant, stop all recurring contributions to the old grant, and point the CLR contributions from the old grant to the new grant.. if that sounds ok to u guys, go ahead and create the new grant and ill do the rest
technically; this would mean adding a new nullable foreign key from grant model called grant.defers_clr_to and then if it exists then all CLR contributions to the old grant are counted towards the new grant.
does this sound like an ok architecture? i think i can code it up + add it to the clr script, but @fronk ud have to add it to the postgres queries

Refers/Fixes

https://gitcoincore.slack.com/archives/CBDTKB59A/p1569423185076200

Testing

tested locally

[codecov]

Codecov Report

Merging #5268 into master will increase coverage by <.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #5268      +/-   ##
==========================================
+ Coverage   29.81%   29.81%   +<.01%     
==========================================
  Files         233      233              
  Lines       19443    19445       +2     
  Branches     2782     2782              
==========================================
+ Hits         5797     5798       +1     
+ Misses      13407    13405       -2     
- Partials      239      242       +3

Impacted Files	Coverage Δ
app/grants/clr.py	0% <0%> (ø)	⬆️
app/grants/models.py	60.98% <100%> (+0.1%)	⬆️
app/dashboard/views.py	13.35% <0%> (ø)	⬆️
...rketing/management/commands/no_applicants_email.py	0% <0%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4cf5f68...ee9ac48. Read the comment docs.