sealing: fix: Make DataCid resource env vars make more sense

[magik6k]

Related Issues

Fixes #9213

Proposed Changes

• Make it possible to set resource table entries for all seal proof types with resource env-vars with no sector size
  • e.g. UNS_MAX_PARALLELISM instead of UNS_2K_MAX_PARALLELISM
  • Env-vars which include sector size will be preferred to the ones applying to all sizes
• Scream loudly when resource env-vars with sector-size are used for DataCid/DC

NOTE: There's a bunch of noise in this PRs, likely coming from a new version of gofmt / goimports having new opinions about code comments..

Checklist

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

• All commits have a clear commit message.
• The 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, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, test
  • area: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps
• This PR has tests for new functionality or change in behaviour
• If new user-facing features are introduced, clear usage guidelines and / or documentation updates should be included in https://lotus.filecoin.io or Discussion Tutorials.
• CI is green