Issue #3609664: Archive settled orders and gate deletion on archive (active, settled, archived, deleted)

Implements #3609664.

Gives operators an explicit order lifecycle: active -> settled -> archived -> deleted.

• archived timestamp base field on the order, with isArchived/getArchivedTime/setArchived and OrderManager archiveOrder/unarchiveOrder/isSettled (only a settled order, cancelled/completed/unused, is archivable).
• Delete guard: deletable only once the order is archived or cancelled (a void order needs no archive step first), keeping the tenant and no-running-workflow checks; the old cancelled-or-all-past rule is dropped.
• Archive/Unarchive operator actions per row (OrderTransitionForm operations + routes) and in bulk; the orders overview hides archived orders by default with a Show archived filter.
• Honest confirm/cancel messages when nothing changed, instead of a false success.

Kernel tests cover archiving a settled order, the archive-gated delete, direct delete of a cancelled order, and that an active order is neither archivable nor deletable. Docs (concepts) and French translations updated.