design(app,deskpie): add country-aware global field policy core

[keIIy-kim]

Background

We separated lookup core from country-aware field policy on purpose.
The new shared lookup core is the prerequisite, but global CRM/forms are still not consistently country-aware.

Today the codebase still has mixed behavior:

• address UI is mostly KR vs others
• phone validation/formatting is still Korean-first in some flows
• business/corporate registration numbers are not modeled as country-aware policies
• app and deskpie do not share one global field policy contract yet

Goal

Introduce a shared country-aware field policy core for globally sensitive inputs.

The core should drive:

• address field shape and validation
• phone number formatting/validation strategy
• business registration / corporate registration input strategy
• country-specific labels, placeholders, and optionality
• cascading form behavior once country changes

Why

We are a global product. If an input is country-sensitive and the implementation is not country-aware, that is a bug.
We need one extensible policy seam instead of ad-hoc KR branching and per-form exceptions.

Scope

In scope

• define shared frontend policy contract under @deck/app
• audit current app + deskpie forms that handle address / phone / registration numbers
• identify country-sensitive fields that are still hard-coded or Korean-first
• design per-country policy resolution flow
• wire the first consumers to the shared policy seam

Out of scope

• lookup core (handled separately)
• broad backend schema redesign without a concrete migration plan

Current hotspots

app

• frontend/app/src/shared/globalization/global-contact-fieldset.tsx
• frontend/app/src/shared/globalization/policy-runtime.ts
• frontend/app/src/features/users/user-form/
• frontend/app/src/shared/utils/validation/

deskpie

• frontend/deskpie/src/pages/companies/company-edit-modal.tsx
• contact / contracting-party / deal forms that still assume flat or Korean-first inputs

Acceptance criteria

• a shared country-aware policy contract exists and is documented
• country-sensitive fields are explicitly identified and tracked
• at least one end-to-end consumer path uses the new policy core
• remaining gaps are listed with follow-up tasks, not hidden in local exceptions

[keIIy-kim]

#703 기준으로 follow-up 범위를 다시 좁혔습니다.

이번 PR에서 이미 반영된 것:

• shared lookup core (@deck/app/shared/lookup)
• app country-aware field policy core (@deck/app/shared/globalization)
• first consumers
  • app user form
  • deskpie company form
  • deskpie contact form
  • deskpie contracting-party form
• deskpie contact / contracting-party FE/BE/DB countryCode 추가

이슈 #705에서 이제 남은 핵심 gap:

• business registration / corporate registration field의 실제 consumer rollout
  • 지금은 app core policy만 있고 실제 deskpie/app form consumer가 없음
• address schema 재설계
  • 현재 address-aware consumer는 user/company 중심이고, contact/contracting-party는 phone-only country context만 추가된 상태
• 다른 phone-bearing form rollout
  • deal / lead / license-request 등
• country-aware display/formatter 정합성 점검
  • list/detail/read-only surface까지 일관성 점검 필요

현재 우선순위 hotspot:

• frontend/app/src/shared/globalization/country-field-policy.ts
• frontend/app/src/shared/globalization/global-contact-fieldset.tsx
• frontend/app/src/shared/globalization/global-phone-fieldset.tsx
• frontend/deskpie/src/pages/contacts/contact-edit-modal.tsx
• frontend/deskpie/src/pages/contracting-parties/contracting-party-edit-modal.tsx
• business registration consumer가 생길 app/deskpie form 경로