Feature Request: Enforce or Normalize Customer Data to Latin Characters

🔍 Problem Statement
As a Pelcro admin, I experience customer records containing non-Latin characters (Cyrillic, Korean, etc.) in name and address fields, which causes postal fulfillment failures and data matching issues with third-party systems.

💡 User Story
As a platform admin, I want Pelcro to validate or transliterate non-Latin characters in name and address fields at point of entry, so that records are compatible with postal services and integrations requiring Latin characters.

🎯 Definition of Done
- Given a name or address field, when a user submits non-Latin characters, then the system blocks submission with an error or auto-transliterates to the nearest Latin equivalent.
- This change impacts the API (customer create/update validation) and UI (inline field validation).
- Limitations: v1 covers name and address fields only; email and custom fields are out of scope.

---

Problem Statement Some customer records contain non-Latin characters (e.g. Cyrillic, Korean) in names and address fields. This creates operational issues for: Postal fulfillment and mailing houses (unable to process non-Latin scripts) Admin-side customer search and record matching Pelcro currently stores customer input exactly as entered , with no validation, restriction, or transliteration of character sets. User Story As a publisher operations team , we want customer names and addresses to be stored in Latin characters , so that we can reliably search customer records and fulfill postal deliveries without manual corrections or mailing house errors.