harmony storage

[snadrus]

Related Issues

This enables HarmonyTask tasks to express (kind-of-cleanly) the storage needs, the system to atomically reserve each need, and provide the paths to Do() without any API change to existing tasks.

Proposed Changes

• Storage is an interface-like struct on TaskTypeDetails that's used to ensure tasks have what they need
• Storagemgr, A helper, manages locking and naming.

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

[magik6k]

Some comments, but this looks much closer.

[magik6k]

MarkComplete should also have the taskID param

[magik6k]

With the last commit this is sufficient to implement storage reservation mechanism for tasks in the sealing pipeline; I'll open a PR on top of this one with impl ported from my previous PR with the better harmony integration