feat: correct french translations

[Vincent-LAMBERT]

Problem or opportunity

French translations are sometimes bad, not necessary or not done when necessary. I am willing to correct this issue myself.

• Bad translation example: "Finaliser le draft" is not good. We say "la" draft in french.
• Unnecessary translation example: Gold is not translated in the french community (here it is translated as "or")
• Missing translations example: The "understand" button when receiving messages instead of "Ok" or something else

NB: Some french translations are really good though so I suspect that there has been someone that worked on that at some point. Might be interesting to have a responsible by language to check translation when needed.

Proposed solution

Change translation where needed, presumably only in the fr.json file.

UX impact

None

Acceptance criteria

• Every french translation has been checked in the fr.json file

Scope

Other

Approval pre-flight

• I searched existing issues and did not find a duplicate.
• I understand maintainers must add status:approved before implementation starts.
• I will branch from development using type/lowercase-slug if this is approved.
• I identified whether this changes docs, release behavior, licensing, or data provenance.

[TtvNekix]

Solved - #328