Fix translation and fallback issues

[gilluminate]

Closes LJ-387

Description Of Changes

Banner not using translated title of custom consent notices

Code Changes

• Looks for translation first, then falls back if not found
• Better fallback logic for the modal

Steps to Confirm

In Admin UI

1. Add a system like “6sense” or “LiquidM” for TCF Experience to use
2. Create a custom notice by clicking “Add a privacy notice +” button on Privacy Notices page (consent/privacy-notices)
3. Give the Notice a name like “Custom Notice Title”
4. In the translations section at the bottom, give the title an English title like “Custom Notice English Translation”
5. Add a language, like Spanish, and give the title a title like “Aviso personalizado”
6. Add a Data Use to the custom notice “analytics”
7. Save it and on the next screen Enable it
8. Go to Experiences and then the TCF experience
9. Add the Custom Notice Title notice
10. Save it and enable it
11. Visit demo page in EEA geolocation (/fides-js-demo.html?geolocation=eea)
12. Notice that the English translation appears and not “Custom Name Title” in the banner on the left column.
13. Change the language to spanish. custom notice's translation “Aviso personalizado” should appear an not "Custom Name Title"

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
• Followup issues:
  • Followup issues created (include link)
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	⬜️ Ignored (Inspect)	Visit Preview		Feb 20, 2025 4:25pm

[lucanovera]

The code changes look good. I've tested this and I've confirmed the title translations are displaying correctly now. Approved.

[cypress]

fides    Run #12562

Run Properties:   Passed #12562  •  65684337d0: Fix translation and fallback issues (#5775)

Project	fides
Branch Review	main
Run status	Passed #12562
Run duration	00m 50s
Commit	65684337d0: Fix translation and fallback issues (#5775)
Committer	Jason Gill
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	5
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results.
View all changes introduced in this branch ↗︎