refactor(model): Decouple Domain Operations From Direct UI Input

[hcoona]

Introduce IUndoBatchScheduler to decouple UndoSystem from InputSystem.Instance.DispatchOnGestureFinish logic:

• Add IUndoBatchScheduler and ImmediateUndoBatchScheduler for headless/test execution in the model layer.
• Add GestureFinishUndoBatchScheduler in the UI layer to wrap input system behavior.
• Use explicit dependency injection for the scheduler in UndoSystem and configure UndoSystem.DefaultScheduler during app startup in Program.cs.

Decouple hardware key state from Blueprint.cs:

• Introduce BlueprintFormat enum (CompressedBase64, RawJson) to make format intent explicit instead of checking InputSystem.Instance.control.
• Update Blueprint.ToBpString() and BlueprintUtilities to accept the BlueprintFormat parameter.
• Move UI evaluation (InputSystem.Instance.control) appropriately to UI callers (ProductionTableView, ShoppingListScreen) to drive intent.

Close #577

[hcoona]

Tested.

1. "Shopping list" export with/without Ctrl.
2. "Production table" export single blueprint with/without Ctrl.
3. "Export entities to to blueprint" with/without Ctrl.
4. Drag line and Ctrl+Z/Ctrl+Y.

[hcoona]

I'll resolve the conflicts soon.

[shpaass]

Take your time, there is no rush.

[hcoona]

Conflicts resolved and tested.

[hcoona]

Merged upstream/master into this branch and reviewed the integration seams around the PR's decoupling changes.

I specifically checked the post-merge overlap for startup/undo scheduling and blueprint export behavior. The conflict resolution keeps the UI-aware UndoSystem.DefaultScheduler setup before Ui.Start() while also preserving the new upstream fatal logging around UI initialization. I also verified the updated production-table export paths still use BlueprintClipboardContext.RequestedFormat, so the Ctrl-to-raw-JSON behavior remains owned by the UI layer and the model-side blueprint APIs continue to receive an explicit BlueprintFormat.

I did not find any new upstream changes that need additional coverage under this PR's approach, and I did not find a new regression from the merge. The existing project-level Yafc.Model -> Yafc.UI dependency is still pre-existing architecture rather than a new regression introduced by this merge.

Validation: dotnet test .\FactorioCalc.sln --configuration Debug --nologo passes with 419/419 tests.