Persist Printavo order owner attribution

[brycejohnson1417]

Problem

FraterniTees Printavo orders expose the rep-like attribution as the Printavo order owner, but historical and current imported rows mostly do not persist owner data. This prevents the app and alumni referral exports from showing which FraterniTees rep handled an order/customer.

Intended outcome

Persist Printavo owner id/name/email from read-only Printavo order syncs, normalize owner name into the app's order attribution field, and backfill existing Supabase Printavo orders with owner attribution where available.

Acceptance criteria

• Printavo order adapter fetches owner id/name/email for invoices and quotes.
• Runtime import stores owner fields in source_payload and normalized owner name for UI attribution.
• Tests cover owner mapping/import behavior.
• Existing FraterniTees Printavo rows can be enriched without destructive rewrite.
• Alumni referral candidate export can include owner/rep attribution.

Non-goals

• No Printavo write-back.
• No destructive order/account/contact replacement.
• No auth/RLS/schema change unless proven necessary.

Test expectations

• Focused unit/script checks for owner mapping/import.
• Repo verification where feasible.

Architecture impact

Keeps provider-specific owner extraction in the Printavo adapter and normalized runtime attribution in the existing order_record read model.

[linear-code]

BRY-108