feat: api: Clean API for Miners

[snadrus]

This is urgently needed to unblock Curio compatibility with NV23, which is blocking Curio from running on CalibrationNet.

Related Issues

To help Lotus have more of a clean API, this PR:

• Enables access to the latest params without depending on lotus/build (which added bulk and risk to Curio).
• Extracts buildconstants out of lotus/build to enable clean access to that content without the other "build" items.
• "Types" packages (API surface) depend on buildconstants instead of lotus/build
• Rm Curio, including building and testing. (these changes broke it anyway)
• Deprecated access to those vars through lotus/build, but piped them through to change the least code possible

Review is quite easy: the "161 files changed" is mostly deletions.

Proposed Changes

Additional Info

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, 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

[github-actions]

All checks have completed

❌ Failed Check / Check (lint-all) (pull_request)
❌ Failed Test / Test (itest-eth_legacy_transactions) (pull_request)
❌ Failed Test / Test (itest-harmonydb) (pull_request)

[rvagg]

wew, well that evolved quite a bit since first commit I reviewed!
will need to take some time to get my head around these, but passing tests would be good

[snadrus]

We have 2 options for cleaning-up build:

1. move dependency-free build constants out (that API needs). What I did here.
2. Move big dependencies out of build/

I'm open to either.

[snadrus]

@rvagg please review despite conflicts. The nature of this PR is such that conflicts will occur continuously but have an obvious fix.

[snadrus]

There is no new code in here, only moved build-constants to another package as /build is too large and full of unnecessary pieces for Curio.
This will experience modifications continuously, so there's no point in me fixing it until we can commit to the intent.

[rvagg]

Looks good to me now. This does warrant a changelog entry though, particularly the deprecations but it'll be relevant to anyone else wanting to consume some of these without pulling in all the garbage you're now able to avoid.
I'd also appreciate another set of more experienced eyes. @ZenGround0 ?

[ZenGround0]

Not sure what's going on with this test flake or something real: https://github.com/filecoin-project/lotus/actions/runs/9911095972/job/27383006018?pr=12112. Once tests pass I'm ok with this.

not actionable

[rjan90]

As discussed in Slack, I will remove the release/backport label, because we will not be backporting this PR to the v1.28.0 train. Instead we will follow up shipping these changes in a subsequent release fairly quick after the stable v1.28.0 is out on July 23rd.