chore(i18n): update french po file to match latest pot file version

[ytihianine]

SUMMARY

Update the french po file to match the translation template. The current file has some weird translations and misses some keys from the template.

Steps

[X] Add all missing translation
[X] Check the file compilation
[X] Check the translation typo and meaning
[ ] Define global translation consistency
[ ] Check the translation pertinence (from UI and user actions)

BEFORE/AFTER SCREENSHOTS

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

To get the new values from .pot template, I ran the following command : msgmerge --update superset/translations/fr/LC_MESSAGES/messages.po superset/translations/messages.pot

IMO, there is a huge work to adress on french translation. The same word can use multiple translation which can lead the user to confusion.
Few example
rows => rangées or lignes
dataset => ensemble de données or jeu de données

I suggest to define a single "admited" translation from now on and future evolution. Here is the list for the most common terms which needs consistency.

Eng	French
chart	graphique
dataset	jeu de données
tag	to_define
currency	to_define
plugin	plugin
upload	charger
layers (in context of map)	couche
layers (in context of annotation)	couche
email	to_define
table (in contexte of database)	table
rows	lignes
X-axis	to_define
Y-axis	to_define
Gender user	to_define

Any feedback from french users are welcomed !

[netlify]

✅ Deploy Preview for superset-docs-preview ready!

Name	Link
🔨 Latest commit	6b197a4
🔍 Latest deploy log	https://app.netlify.com/projects/superset-docs-preview/deploys/6a35a1e782888c0008dcd6b4
😎 Deploy Preview	https://deploy-preview-40635--superset-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.77%. Comparing base (9e50d9e) to head (477c827).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #40635      +/-   ##
==========================================
- Coverage   64.78%   64.77%   -0.01%     
==========================================
  Files        2689     2689              
  Lines      148936   148936              
  Branches    34365    34365              
==========================================
- Hits        96481    96474       -7     
- Misses      50690    50694       +4     
- Partials     1765     1768       +3     

Flag	Coverage Δ
hive	39.20% <ø> (ø)
mysql	57.86% <ø> (ø)
postgres	57.92% <ø> (-0.01%)	⬇️
presto	40.73% <ø> (ø)
python	59.32% <ø> (-0.01%)	⬇️
sqlite	57.50% <ø> (ø)
unit	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bito-code-review]

Bito Automatic Review Failed - Technical Failure

Bito encountered technical difficulties while generating code feedback . To retry, type /review in a comment and save. If the issue persists, contact support@bito.ai and provide the following details:

Agent Run ID: e3774216-69d7-44d0-86a0-770a1b33b976

[github-actions]

⚠️ Translation Regression Detected

A source change in this PR renamed or reworded strings, invalidating existing translations (they are now #, fuzzy) in fi, th. Please resolve the affected .po files before merging.

Note: intentionally deleting a translatable string is not a regression and is not flagged here — only translations invalidated by a renamed/reworded source string are.

Language	Fuzzy before	Fuzzy after	New
fi	4818	4823	+5
th	4818	4823	+5

How to fix

1. Install dependencies (if not already set up):

pip install -r superset/translations/requirements.txt
sudo apt-get install gettext   # or: brew install gettext

2. Re-extract strings and sync .po files:

./scripts/translations/babel_update.sh

This rewrites superset/translations/messages.pot from the current source files and merges the changes into every .po file. Strings whose msgid changed will be marked #, fuzzy.

3. Resolve the fuzzy entries in the affected language files (fi, th):

grep -n '#, fuzzy' superset/translations/<lang>/LC_MESSAGES/messages.po

For each fuzzy entry, either rewrite the msgstr to match the new string and remove the #, fuzzy line, or clear the msgstr to "" if you cannot provide a translation.

4. Commit your changes to the .po files.

[rusackas]

@ytihianine thanks for your patience here... a lot has landed on French since this was opened (the AI backfill in #41655 and Jean Pommier's improvements via #41752), so the original diff no longer applied and the file had picked up compile errors against the current template.

Rather than lose your work, I rebuilt the branch on current master keeping what's still valuable: 735 of your human translations now replace AI-generated fuzzy entries and are promoted to confirmed, with your authorship on the commit. Dropped: 35 entries carrying [CHECK] self-annotations, 11 identity passthroughs, and values that conflicted with entries a human already confirmed on master since (happy to revisit any of those individually if you feel strongly). Zero regressions, msgfmt --check passes.

Once CI's green this should be mergeable... and thanks for what turned out to be the largest single human-review contribution to the French catalog.