refactor: introduce upstream choke pressure control strategy

[frodehk]

Summary

• Introduce an UpstreamChokePressureControlStrategy (with runner) as an additional pressure control option.
• Update ASVSolver to allow upstream choke pressure control to be applied after speed selection.
• Make UpstreamChokeSolver robust by adding an endpoint feasibility/bracketing check to avoid root-finding exceptions when the target is not achievable within the upstream ΔP boundary.
• Add unit + integration tests.

Refs:
https://github.com/equinor/ecalc-internal/issues/1595

---

Type of Work

• Patch: X.Y.Z+1. NEGLIGIBLE visible changes, does not change input or output - OR changes behaviour. Use chore:, refactor: etc
• Minor: X.Y+1.Z. Minor changes, might ADD new input (YAML), or other backwards-compatible changes. Use feat:, fix:
• Major: X+1.Y.Z. Major and most likely BREAKING changes, wo. backwards compatibility, or removing temporary backwards compatibility functionality. Use ! or BREAKING:.

See here (internal): https://github.com/equinor/ecalc-internal/discussions/1044

Have you remembered and considered?

• IF FEAT: I have remembered to update documentation
• IF FIX OR FEAT: I have remembered to update manual changelog (docs/drafts/next.draft.md)
• IF BREAKING: I have remembered to update migration guide (docs/docs/migration_guides/)
• IF BREAKING: I have committed with BREAKING: in footer or ! in header
• I have added tests (if not, comment why)
• I have used conventional commits syntax (if you squash, make sure that conventional commit is used)
• I have included the Github issue nr in the footer!

What is this PR all about?

What else did you consider?

Between the lines?