R4R: removed governance slashing

[sunnya97]

closes #2256

• Targeted PR against correct branch (see CONTRIBUTING.md)

• Linked to github-issue with discussion and accepted design OR link to spec that describes this work.

• Wrote tests

• Updated relevant documentation (docs/)

• Added entries in PENDING.md with issue #

• rereviewed Files changed in the github PR explorer

---

For Admin Use:

• Added appropriate labels to PR (ex. wip, ready-for-review, docs)
• Reviewers Assigned
• Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

[codecov]

Codecov Report

Merging #2395 into develop will decrease coverage by 0.42%.
The diff coverage is 85.71%.

@@             Coverage Diff             @@
##           develop    #2395      +/-   ##
===========================================
- Coverage    63.54%   63.12%   -0.43%     
===========================================
  Files          120      120              
  Lines         7236     7224      -12     
===========================================
- Hits          4598     4560      -38     
- Misses        2326     2350      +24     
- Partials       312      314       +2

[ValarDragon]

Hrmm. An interesting consequence of this is that the the simulator will no longer catch a significant portion of the slashing bugs its been finding, until we fix #2320. This is because they were all being caught on governance slashing, and only execute after a slashing occurred. We'll have to do a bunch more work to now test our staking code, but thats nbd. I'll make a follow-up issue

[alexanderbez]

utACK -- thanks!

[cwgoes]

utACK but waiting to merge for the moment (want to wait for simulation updates re @ValarDragon's comment)

[alexanderbez]

Ref: #2396

[cwgoes]

Ref: #2396

Thanks. Merging now, let's make sure to address #2396 before releasing the next version.