Integrate reviewed PR backlog and reconcile table lifecycle fixes

[sridharkalaibala]

Resolve overlapping table-close and cancellation fixes before merging the open PR backlog into develop. Paid tables retain the current opt-in cleaning policy; interrupted closures retain their explicit choice, and a committed cancellation remains successful while floor cleanup retries. Preserve develop's existing release version and settings page.

Includes #1092, #1091, #1090, #1089, #1076, #1069, #1036, #1033, #1032, #1031, #1030, #1019, #1001 and #970. Their original heads are retained in the merge history. This also brings in printable-menu export responsiveness, synthetic connector fixtures and dependency updates. #1094 remains the separate develop-to-main release PR.

Validation:

• Desktop: 3,898 passed, 5 skipped.
• API: fresh full run passed 500 suites and 12,512 tests; 13 tests remain skipped by the existing configuration. Focused table/cancellation/startup verification also passed all 208 tests.
• API lint: no errors; existing warnings remain. Formatting and generated API docs pass.
• Frontend production bundle, packaged module/runtime/declared dependency checks and attribution pass.
• The upload-sarif v4.38.2 annotated upstream release tag was dereferenced and matches the new pinned commit. Updated its allowlist regression check.
• JSDOM's equivalent computed bold value (700) is accepted without weakening the receipt layout assertions.

No release publication or live customer data changes. Existing root npm audit findings (Electron and a transitive package) remain outside these PR updates; API audit reports zero vulnerabilities.

[github-actions]

Merged to develop. Anyone can test this - you do not need write access.

Try it at https://develop.posnic.io, or run it yourself:

git fetch origin develop && git checkout develop
npm install && npm --prefix api install
npm run dev   # then http://localhost:3000

When you have tested it, say what you did and what happened, and set
QA passed or QA failed. If you cannot set labels, just comment -
a maintainer will.

Reporting that something is broken is as useful as fixing it. It is
better found here than by a shopkeeper.