feat(Localization): add pt-BR localization

[hernanyoliveira]

Link issues

fixes #7550

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

New Features:

• Introduce initial pt-BR localization file for future Brazilian Portuguese translations.

[bb-auto]

Thanks for your PR, @hernanyoliveira. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a new Brazilian Portuguese localization resource file to the project for UI text translation.

File-Level Changes

Change	Details	Files
Introduce a new localization file for Brazilian Portuguese translations.	Create a new JSON resource file for the pt-BR locale Define key-value pairs for localized strings in Brazilian Portuguese following existing localization conventions Integrate the new locale file into the existing localization asset structure so it can be loaded by the app/runtime	localization/pt-BR.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The PR description still contains the template placeholders (e.g., fixes #{issue number}, empty risk/verification justifications); please fill these in so reviewers understand the context and impact of this change.
• For the new pt-BR.json file, ensure its key structure and naming are consistent with existing localization files (e.g., en.json) so it can be plugged into the localization pipeline without special handling.
• If this localization file is intended to be functional rather than just a placeholder, make sure it is registered or referenced wherever supported locales are configured so the new locale can actually be selected at runtime.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The PR description still contains the template placeholders (e.g., `fixes #{issue number}`, empty risk/verification justifications); please fill these in so reviewers understand the context and impact of this change.
- For the new `pt-BR.json` file, ensure its key structure and naming are consistent with existing localization files (e.g., `en.json`) so it can be plugged into the localization pipeline without special handling.
- If this localization file is intended to be functional rather than just a placeholder, make sure it is registered or referenced wherever supported locales are configured so the new locale can actually be selected at runtime.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (56ff312) to head (dfcbef3).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #7569   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          749       749           
  Lines        32976     32976           
  Branches      4580      4580           
=========================================
  Hits         32976     32976           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.