[Brave News]: Bump Nala to fix ButtonMenu bug

[fallaciousreasoning]

Resolves brave/brave-browser#40621

This only has one change for Nala, which is the fix for the ButtonMenu:

brave/leo@765fc13...7de60c1

Note: The commit lives on a new 1.69 branch in Nala, not on main so we don't pull in any unnecessary changes.

This commit is the fix.

We can't uplift the Nala bump from 1.70.x because it has a bunch of color changes.

Submitter Checklist:

• I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
• 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 wiki
  • npm run presubmit wiki, 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/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. Open Brave News on the NTP
2. The ButtonMenu should have a 3 dot menu, not the text "Click Me"

[kjozwiak]

Verification PASSED on Win 11 x64 using the following build(s):

Brave | 1.71.24 Chromium: 128.0.6613.85 (Official Build) nightly (64-bit)
-- | --
Revision | 71ea50704534831db1a46c24098f0076eccfb120
OS | Windows 11 Version 23H2 (Build 22631.4037)

Using the STR/Cases outlined via #25289 (comment) & brave/brave-browser#40621 (comment), ensured that the button on the news articles is appearing as ... rather than Click me.

• ensured that clicking on ... produced/displayed a context menu allowing you to remove/hide content
• ensured that clicking on Hide content from [xyz] removes that particular publisher
  • also ensured that you have the ability to refresh the feed with the New content available. Reload? button
• ensured that the correct button is still being displayed after opening/closing several NTP and viewing the News Feed
  • ensured restarting the browser several times still displays the correct button within the news feed

Example	Example

[kjozwiak]

Uplift into 1.69.x approved 👍 QA has verified the PR on Nightly via 1.71.x as per #25289 (comment).