i18n(fr): add missing translations in assets.json

[RamyDerouiche]

This PR adds the missing French translations for the assets.json locale file and translates a couple of keys that were still in English.

Added (5 keys)

• additional_data → "Données supplémentaires"
• asset_many → "Assets"
• asset_one → "Asset"
• scheduling → "Planification"
• taskDependencies → "Dépendances des tâches"

Translated (2 keys that were still in English)

• extra: "Extra" → "Supplémentaire"
• group: "Group" → "Groupe"

Notes

• The terms Asset / Assets are kept in English to follow the existing convention in the French locale (e.g. existing entries "événement d'Asset", "Rechercher des Assets").
• This PR only adds the missing entries; pre-existing translations in this file were left unchanged to keep the scope focused. Any typo or wording fixes can follow in a separate PR.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

[potiuk]

@RamyDerouiche A few things need addressing before review — see our Pull Request quality criteria.

• ❌ Pre-commit / static checks — Failing: CI image checks / Static checks. See docs.

No rush.

---

Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you.

---

Drafted-by: Claude Code (Opus 4.7); reviewed by @potiuk before posting

[pierrejeambrun]

Thanks for the PR.

This was done as part of #67240 that globally update the french translation.

Closing