fix: preserve user-customized object/field names across locale changes

[jnMetaCode]

Summary

• Fixes user-customized Data Model object and field names being overwritten by i18n translations when the UI language is changed
• Changes the resolution priority so direct standardOverrides (user customizations) always take precedence over locale-specific translations and auto i18n translations
• For field metadata, removes the SOURCE_LOCALE-only restriction that was preventing customizations from being applied in non-English locales

Root Cause

In resolveObjectMetadataStandardOverride and resolveFieldMetadataStandardOverride, the priority order was:

1. standardOverrides.translations[locale] (locale-specific translations)
2. standardOverrides[labelKey] (user customizations)
3. Auto i18n translation fallback

For field metadata, the direct override check (step 2) was additionally gated behind locale === SOURCE_LOCALE, meaning user customizations were completely ignored in non-English locales.

The fix reorders the priority to:

1. standardOverrides[labelKey] (user customizations)
2. standardOverrides.translations[locale] (locale-specific translations)
3. Auto i18n translation fallback

This ensures that when a user renames "Company" to "ASTF", that name persists regardless of the active UI locale.

Test plan

• Updated existing unit tests in resolve-object-metadata-standard-override.util.spec.ts
• Updated existing unit tests in resolve-field-metadata-standard-override.util.spec.ts
• Set UI language to English, rename a standard object (e.g., Company → ASTF), switch to German — ASTF should persist
• Set UI language to German, rename a standard object — the custom name should persist after refresh
• Verify that uncustomized standard objects still show translated labels in non-English locales

Fixes #18950

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[github-actions]

Welcome!

Hello there, congrats on your first PR! We're excited to have you contributing to this project.
By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement.

Generated by 🚫 dangerJS against e8cdf1d

[cubic-dev-ai]

No issues found across 4 files

[jnMetaCode]

Closing this PR. Apologies for the noise — I'll take more care to ensure quality and proper testing before submitting future contributions.