Set fixed 10 min interval to update news items

[atuchin-m]

Resolves brave/brave-browser#42021

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:

[brave-builds]

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

[fallaciousreasoning]

Approving so we can land asap

[fallaciousreasoning]

Maybe do a Math.max instead?

Suggested change

	updatesIn: 10 * minute,
	updatesIn: Math.max(10 * minute, duration - (Math.abs(diff - amount))),

[brave-builds]

Released in v1.73.69

[kjozwiak]

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

Brave | 1.73.75 Chromium: 131.0.6778.24 (Official Build) nightly (64-bit)
-- | --
Revision | c3d6b9bdbbdf63fc4831eb0bc8e116e9742e3852
OS | Windows 11 Version 24H2 (Build 26100.2161)

Using the STR/Cases outlined via brave/brave-browser#42021 (comment), ensured that the CPU & GPU are not spiking/increasing to unreasonable levels while idling on a NTP with News enabled as per the following:

• ensured that the CPU/GPU never increased more than ~5% using 1.73.75 Chromium: 131.0.6778.24
  • in my case, the CPU/GPU never increased more than 2% with the the above build which has the fix
  • with 1.73.68 Chromium: 131.0.6778.14 which doesn't have the fix, the CPU/GPU was reaching ~30% at times while idling

1.73.68 Chromium: 131.0.6778.14	1.73.75 Chromium: 131.0.6778.24

The above was also verified on Nightly by @atuchin-m as per brave/brave-browser#42021 (comment).