Fix auto-closing orders withdrawal

[JasonMHasperhoven]

• Addresses Fix batch withdrawal to work with auto-closing positions #241
• And splits positions into multiple files for better maintenance

[erwanor]

👍

[erwanor]

LGTM, can merge on resolving conflicts

[TalDerei]

few questions cc @erwanor

1. Is this scope intended to handle both batch closes and batch withdrawals, or just batch withdrawals? It errors on performing a batch close.

---

2. why can't I close my last liquidity position?

Screen.Recording.2025-01-16.at.7.24.15.PM.mov

---

3. is the batch withdrawal feature not working because the last liquidity position isn't closed?

Screen.Recording.2025-01-16.at.7.24.25.PM.mov

[erwanor]

Batch withdrawals can fail for approximately two reasons:

• an auto closing position has been closed by the dex engine: this is an ordinary usecase that is hit by almost every user of close_on_fill positions.
• we construct a TPR that contains an LP that belongs to a different subaccount, this is somewhat of an edgecase.

This PR fixes 1), and leaves 2) for later. It will be easy to solve 2) when we get to the beta because we will have made changes to the view service, beginning with penumbra-zone/penumbra#4992

This PR is called "Fix batch withdrawal" but it should rather be named, fix auto-closing orders withdrawal.

[cronokirby]

(added a conflict-resolution commit)

[cronokirby]

Seems good ; I think it would've been simpler to just close all positions, eliminating the need to thread the state around, but this works fine as well, and can save on gas.