fix: params: Update SupportedProofTypes to the correct ones

[rjan90]

It was noted by Hubert that Filecoin.StateGetNetworkParams returns the wrong SupportedProofTypes:

Example:

curl -X POST 'http://127.0.0.1:1234/rpc/v0' \
>     -H 'Content-Type: application/json' \
>     --data '{"jsonrpc":"2.0","id":1,"method":"Filecoin.StateGetNetworkParams","params":[]}'
{"jsonrpc":"2.0","result":{"NetworkName":"mainnet","BlockDelaySecs":30,"ConsensusMinerMinPower":"10995116277760","SupportedProofTypes":[3,4],"PreCommitChallengeDelay":150,"
------
UpgradeWatermelonHeight":3469380,"UpgradeDragonHeight":3855360,"UpgradePhoenixHeight":3855480},"Eip155ChainID":314},"id":1}

Proposed Changes

Update the SupportedProofsTypes in build/params_* to the correct set of ProofTypes supported in the different networks.

Additional Info

Given that nobody has not complained about this earlier, it brings the question if this field is worth keeping?

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[rvagg]

I assume these changed at some network upgrade, but the method doesn't take an epoch, tipset or anything else that could be used to give different results. So this change seems reasonable given "now" is the only reasonable way of interpreting a request.