Support json parsing of epoch-rewards partition data sysvar accounts

[CriesofCarrots]

Problem

New epoch rewards partition-data sysvars aren't parsed, even though all the other accounts owned by Sysvar1111111111111111111111111111111111111 are.

Summary of Changes

Implement parsing

$ curl  -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0", "id":1, "method":"getAccountInfo", "params":["FdAGcHUFksSVgNj5ihPaddMet3cuuFwJsxkG6ZXVA4Ly", {"encoding":"jsonParsed","commitment":"confirmed"}]}' 127.0.0.1:8899 | jq
{
  "jsonrpc": "2.0",
  "result": {
    "context": {
      "apiVersion": "1.18.0",
      "slot": 831
    },
    "value": {
      "data": {
        "parsed": {
          "info": {
            "numPartitions": 18,
            "parentBlockhash": "8m6GQ3auZGBMKsqcShxSqzUhuUpATJmXbbn3FqKYFdQp",
            "version": 0
          },
          "type": "epochRewardsPartitionData"
        },
        "program": "sysvar",
        "space": 44
      },
      "executable": false,
      "lamports": 1197120,
      "owner": "Sysvar1111111111111111111111111111111111111",
      "rentEpoch": 0,
      "space": 44
    }
  },
  "id": 1
}

Fixes #

[codecov]

Codecov Report

Attention: 10 lines in your changes are missing coverage. Please review.

Comparison is base (e74f04a) 81.6% compared to head (ae187cd) 81.6%.
Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #34914     +/-   ##
=========================================
- Coverage    81.6%    81.6%   -0.1%     
=========================================
  Files         827      827             
  Lines      223846   223859     +13     
=========================================
- Hits       182823   182807     -16     
- Misses      41023    41052     +29     

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.