fix: curio: Drop FKs from pipeline to fix retry loops

[magik6k]

Related Issues

Much simpler approach to #11959

Proposed Changes

Not handled in poller yet, tho any handling strategy will likely be "just wait for user action" initially until we develop smarter repair logic.

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

[LexLuthr]

LGTM!

[LexLuthr]

This will basically leave all bad sectors in the pipeline table and poller won't touch them.
For the retry strategy, we can allow a manual UI retry for upto 72 hours(or less). After that, we should probably clean up and get back the storage resources.
We can generate an alert for such sectors to make it easier for users.