[T2859] - Provide hardcoded products data with multilanguage support

[SlWa99]

MyCompassion Product Data Integration with Multilingual Support

Purpose and Context

The goal of this PR is to automate the configuration and translation of products related to MyCompassion.
It ensures that all environments (Development, Staging, Production) are consistently populated with synchronized product data, descriptions, and impact statements without requiring manual setup.

This approach guarantees data consistency across environments and reduces maintenance overhead.

---

Applied Changes and Improvements

1. Centralized Product Data Integration

• XML data definition
  Introduction of the product_funds_data.xml file to define and manage the 7 core MyCompassion products:

  • WASH
  • Waiting Children
  • Health
  • Food Aid
  • Emergency
  • Christmas
  • Survival

• Full MyCompassion coverage
  The integration includes:

  • MyCompassion tab configuration (colors, pictograms, impact points)
  • General Information fields (product type, category, sale price, internal reference, etc.)

---

2. Existing Data Mapping (OpenUpgrade)

• Pre-migration script implementation
  A pre-migration script has been added to:
  • Link existing production products (via database IDs) to the new XML IDs
    This allows the codebase to take ownership of previously manually created products and prevents duplicates.
  • Clean up legacy donation.impact.line and donation.info.line records to ensure a clean and non-duplicated import of the new content.

---

3. Multilingual Support

• Complete translations
  Full translations have been added for FR, DE, and IT using .po files.

• Translated content includes

  • Product names
  • MyCompassion descriptions
  • Impact points
  • Product-specific information lines

---

4. Visual Identity Alignment

• Unified design assets
  Colors and pictograms are sourced from the theme_compassion_2025 module to ensure a consistent visual identity across the My2 interface.

---

Technical Notes on IDs

• Fixed ID strategy
  After validation with @ecino, fixed database IDs are used in the migration script to precisely target existing production records.

• Environment safety
  If a targeted ID does not exist (e.g. in a fresh environment), Odoo automatically creates the record from the XML data, ensuring compatibility across all environments.

[gemini-code-assist]

Summary of Changes

Hello @SlWa99, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automates the configuration and translation of MyCompassion product data, ensuring consistent and synchronized product information across all environments. It streamlines data management by centralizing product definitions in XML, handling existing data migration, and providing comprehensive multilingual support, thereby reducing manual setup and maintenance.

Highlights

• Centralized Product Data: Introduced product_funds_data.xml to define and manage 7 core MyCompassion products (WASH, Waiting Children, Health, Food Aid, Emergency, Christmas, Survival) with comprehensive configuration.
• Pre-migration Script: Implemented a script to link existing production product IDs to new XML IDs, clean up legacy donation.impact.line and donation.info.line records, and manage XML IDs for data consistency.
• Multilingual Support: Added full translations for product names, MyCompassion descriptions, and impact points in French (FR), German (DE), and Italian (IT) via .po files.
• Visual Identity Integration: Ensured consistent visual branding by sourcing colors and pictograms from the theme_compassion_2025 module.
• Robust ID Management: Utilized a fixed ID strategy for existing records, with Odoo automatically creating records from XML data in fresh environments, ensuring compatibility.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively centralizes MyCompassion product data into a dedicated XML file, complete with multilingual support and a well-thought-out pre-migration script. The changes will improve data consistency and maintainability. I've provided several suggestions to enhance the consistency of product data definitions within the new XML file and to refine a parameter in the migration script for better long-term stability. Overall, this is a solid contribution.