Frontend browser-print receipt settings remain stale until Settings page is opened (ARCH-011b) #1188

Problem description

In the frontend/browser-print receipt workflow, receipt settings (such as business address, phone, tax registration number, footer message, and visibility flags) stored in posSettings (frontend/src/store/pos-settings.ts) are only hydrated from backend settings when navigating to the Settings page (frontend/src/app/(dashboard)/settings/page.tsx:2120-2137).

Until an operator visits the Settings page, the browser print path uses default or stale Zustand/localStorage values, resulting in missing or incorrect receipt headers/footers in browser-printed bills.

Root cause

Hydration functions (setBillAddress, setBillPhone, setBillTaxRegistrationNumber, setBillShowAddress, etc.) are coupled to loadBusiness() inside settings/page.tsx instead of running during application initialization or authenticated POS layout hydration.

Acceptance criteria

• Receipt display settings are hydrated consistently from the backend upon initial dashboard/POS layout load or tenant settings fetch.
• Browser print output reflects current backend store settings without requiring a visit to the Settings page first.
• Terminal-local hardware settings (e.g. printer paper size, local ESC/POS device) remain preserved.
• Thermal printing path behavior remains unchanged.