fix: sealing: FinalizeSector doesn't need sealed replica access

[magik6k]

Related Issues

Probably fixes some of the "stuck in finalize" issues

Proposed Changes

FinalizeSector doesn't touch the sealed sector file, so requiring it to exist on the worker next to the cache can only cause issues - for example when a sector was in the middle of being finalized, the sealed file might have been moved off the worker just before it restarted - causing Finalize to restart, and get stuck on the early stage which expects sealed/cache files to still be on the worker - where we only really need the cache

Additional Info

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.
• [hopefully] CI is green

[ZenGround0]

Double checking: this doesn't apply in FinalizeReplicaUpdate because we do a MoveStorage call on the sealed replica and the worker needs access to the sector to do the move?

[magik6k]

Correct