fix: i18n: standardize trigger events terminology in billing translations

[NeatGuyCoding]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fix i18n: unify trigger events terminology in billing translations

• Standardize Italian (it-IT) to "eventi di attivazione"
• Standardize Portuguese (pt-BR) to "Eventos de Gatilho" and translate "workflow"
• Fix Romanian (ro-RO) typo: "EVENIMENTE TRIGER" → "EVENIMENTE DECLANȘATOARE"

Screenshots

Before	After
...	...

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[gemini-code-assist]

Summary of Changes

Hello @NeatGuyCoding, 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 aims to enhance the internationalization (i18n) of billing-related texts by unifying the terminology for 'trigger events' across Italian, Portuguese (Brazil), and Romanian translations. The changes ensure a more consistent and accurate user experience in these languages by correcting existing translations and addressing a specific typo, thereby improving clarity and standardization.

Highlights

• Italian (it-IT) Translations: Standardized the term 'trigger events' to 'eventi di attivazione' for consistency across billing-related phrases, including 'unlimited trigger/workflow' and modal titles.
• Portuguese (pt-BR) Translations: Standardized 'trigger events' to 'Eventos de Gatilho' and corrected the translation of 'workflow' to 'fluxo de trabalho' in relevant billing contexts, ensuring unified terminology.
• Romanian (ro-RO) Translations: Fixed a typo in the 'usageTitle' for trigger events, changing 'EVENIMENTE TRIGER' to the correct 'EVENIMENTE DECLANȘATOARE'.

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 standardizes the terminology for 'trigger events' in the billing translations for Italian, Portuguese, and Romanian. The changes are mostly correct and achieve the goal of unification. I've pointed out a minor capitalization inconsistency in the Portuguese translation to ensure it aligns with the other languages.

[gemini-code-assist]

For consistency with other languages and the original English text ('Upgrade to unlock more trigger events'), 'Eventos de Gatilho' should probably be in lowercase here as 'eventos de gatilho'. The term is part of a sentence, not a standalone title.

Suggested change

	title: 'Atualize para desbloquear mais Eventos de Gatilho',
	title: 'Atualize para desbloquear mais eventos de gatilho',

[Copilot]

Pull request overview

This PR standardizes the translation of "trigger events" terminology across Italian, Portuguese, and Romanian billing translation files to ensure consistency within each language. The changes fix a typo in Romanian and unify terminology that was previously inconsistent.

• Fixes Romanian typo from "TRIGER" to "DECLANȘATOARE"
• Standardizes Italian to consistently use "eventi di attivazione"
• Standardizes Portuguese to consistently use "Eventos de Gatilho" and translates "workflow" to "fluxo de trabalho"

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
web/i18n/ro-RO/billing.ts	Corrects typo "EVENIMENTE TRIGER" → "EVENIMENTE DECLANȘATOARE" in usageTitle
web/i18n/pt-BR/billing.ts	Standardizes "trigger events" to "Eventos de Gatilho" across multiple fields and translates "workflow"
web/i18n/it-IT/billing.ts	Standardizes "trigger events" to "Eventi di attivazione" across all occurrences

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The term 'Gatilhos' should be standardized to 'Eventos de Gatilho' to maintain consistency with the other changes in this PR. The English version uses 'Triggers/workflow', which should translate to 'Eventos de Gatilho/fluxo de trabalho ilimitados' for consistency with line 100 and the rest of the file.

Suggested change

	unlimited: 'Gatilhos/fluxo de trabalho ilimitados',
	unlimited: 'Eventos de Gatilho/fluxo de trabalho ilimitados',

[Copilot]

The phrase 'limita de declanșatoare de evenimente' is grammatically awkward in Romanian. It should be 'limita de evenimente declanșatoare' (moving the adjective after the noun) or 'limita evenimentelor declanșatoare' to match natural Romanian word order and be consistent with the English 'limit of workflow event triggers'.

Suggested change

	description: 'Ai atins limita de declanșatoare de evenimente de flux de lucru pentru acest plan.',
	description: 'Ai atins limita de evenimente declanșatoare de flux de lucru pentru acest plan.',