Add translations for Brave News channel names

[fallaciousreasoning]

Resolves brave/brave-browser#26116

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

1. Enable the Brave News V2 flag
2. In a non-English locale, open the Brave News configure dialog
3. Channels should be translated

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[sangwoo108]

LGTM!

[sangwoo108]

Q. Can we rename props.channelId to props.channelName? The id seems to be used as name as well but I think renaming would be good 😄

[fallaciousreasoning]

Renamed! Mind taking another look?

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[fallaciousreasoning]

I've renamed the remaining channelIds to channelNames - mind taking another look?

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[sangwoo108]

still LGTM! Thanks :)

[brave-builds]

A Storybook has been deployed to preview UI for the latest push

[stephendonner]

@fallaciousreasoning just to be sure, these are what you're referring to, right?

@mkarolin will we have to wait until near-end of this release cycle, to be able to test these translations, if you know?

[fallaciousreasoning]

Yup, those are the ones :)

[stephendonner]

Verified PASSED using

Brave	1.47.48 Chromium: 107.0.5304.91 (Build oficial) nightly (x86_64)
Revisión	3d5948960d62418160796d5831a4d2d7d6c90fa8-refs/branch-heads/5304@{#1097}
SO	macOS Versión 13.1 (Fase 22C5033e)

Steps:

0. set my macOS system language to Spanish
1. installed 1.47.48
2. launched Brave
3. opened brave://flags
4. set brave://flags/#brave-news-v2 to Enabled
5. clicked Relaunch
6. opened a new-tab page
7. clicked on Customize
8. clicked on Brave News
9. examined the Customize Brave News dialog

Confirmed the start of translated channel names, e.g. Crypto -> Criptomonedas in the dialog