Ship Workflow large-history MySQL fixes in Server 2.3.14

[rmcdaniel]

User-visible fix

Pins published Workflow 2.0.16 so large inline histories no longer exhaust MySQL sort memory during history-budget repair or worker history pagination. Database limits, payload limits, page order, and leases are unchanged.

Updates the source release manifest to Server 2.3.14 / Helm chart 0.1.93 and regenerates the existing Compose/Kubernetes defaults. No unrelated package updates or Server application changes.

References durable-workflow/workflow#515 and durable-workflow/workflow#517.

Qualification and publication

• Workflow native MySQL regression: 38 tests / 244 assertions at the default 262144-byte sort buffer and regex work limit 32.
• Exact upstream source full CI passed: https://github.com/durable-workflow/workflow/actions/runs/35653547611 .
• Three PHP SDK 2.0.11 candidate runs passed 376832-byte values through real activities; this used source overlays and is not final-image proof.
• Composer resolves published Workflow 2.0.16 at 025f2469e8151d44df2350c722e765e5780c08c6; no dependency security advisories. Source-release synchronization passes.
• Server CI, immutable image/chart publication, and the same journey against the published image without overlays remain to finish before the owning issue closes.

Unchanged SDKs do not need alignment releases. Sample App will receive the qualified Server/Workflow tuple after image publication.