Description

This PR introduces full French localization for the application and implements the Post-Download Share Vector, designed to drive organic growth by prompting users to share PDFLince at their moment of highest satisfaction.

Key Implementations:

• Full French Localization: Added comprehensive French translations across the entire application, including the main dictionary (fr/index.ts), FAQs (fr/faqs.ts), operations metadata (fr/operations.ts), and corresponding routing layouts.
• Web Share API Integration: Added a native share button to ProcessingStatusDialog.tsx. If the browser supports it, it opens the native share sheet. If not, it falls back to a graceful navigator.clipboard.writeText() action with a temporary "Copied!" state.
• Localized Share Prompts: Expanded dictionary-types.ts and updated all 6 language dictionaries (EN, ES, FR, DE, PT, IT) with high-converting, value-driven copy targeting users' most popular actions (split, compress, merge, convert).
• README Cleanup: Removed emojis from README.md to establish a more professional, open-source aesthetic.

Fixes # (Leave blank or add issue number if you have one tracked)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Localization Verification: Verified that all French routes (/fr, /fr/faq, etc.) render correctly without missing dictionary keys, and that the hreflang tags point to the correct localized URLs.
• Web Share API Verification: Tested the UI rendering of the Share button upon successful PDF processing. Verified that navigator.share correctly receives the title, text, and url parameters.
• Fallback Clipboard Verification: Verified that environments lacking Web Share API support correctly trigger the clipboard copy mechanism and temporarily display the localized "Copied!" label.
• Type Safety & Build Integrity: Ran npm run build locally. Verified that the ProcessingStatusDialogProps strictly adhere to the new SharePromptStrings interface without throwing ESLint or TS compilation errors.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes