Upgrade from Chromium 121.0.6167.57 to Chromium 121.0.6167.75.

[mkarolin]

Resolves brave/brave-browser#35382

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 lint, 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:

[github-actions]

[puLL-Merge] - brave/brave-core@21600

Description

This PR introduces various text and UI-related updates in Brave's New Tab Page and other parts of the browser interface. These changes include adding tool-tips, improving accessibility labels, and updating messages related to AI-generated themes and tab organization features. There is also a version bump for the underlying Chromium engine, and several additions and changes to resource files.

Changes

Changes

app/generated_resources.grd

• Added new messages for color hue slider delete button in IDS_NTP_CUSTOMIZE_COLOR_HUE_SLIDER_DELETE_TITLE and IDS_NTP_CUSTOMIZE_COLOR_HUE_SLIDER_DELETE_A11Y_LABEL.
• Updated accessibility labels for wallpaper search history results with various descriptors.
• Removed message IDS_NTP_WALLPAPER_SEARCH_HISTORY_TILE_TITLE.
• Added messages for unselecting a subject, mood, and style in wallpaper search.
• Added messages for loading and success states in AI-generated wallaper search.
• Removed some obsolete messages and added descriptions and titles for various AI features.

app/settings_strings.grdp

• Minor text update: changed "Tab Organizer" to "Tab organizer".

browser/ui/views/brave_tab_search_bubble_host.(cc|h)

• Modified ShowTabSearchBubble to accept an additional tab_index parameter.

chromium_src/net/tools/transport_security_state_generator/input_file_parsers.cc

• Updated timestamp and pins list for certificates.

components/site_settings_strings.grdp

• Added new entries related to site performance settings.

package.json

• Updated Chromium tag version from 121.0.6167.57 to 121.0.6167.75.

patches/*

• The patches seem to be updates to existing patch files. It would require reviewing the Brave codebase to understand the context and necessity of these patches.

Security Hotspots

• chromium_src/net/tools/transport_security_state_generator/input_file_parsers.cc: Changes in certificates and timestamp need to be carefully reviewed to ensure no unauthorized or rogue certificates are being introduced.
• package.json: Since this PR updates the underlying Chromium engine version, it is crucial to review the Chromium change logs for any security-related updates or patches that have been included.
• patches/: Patches that modify the core functionality, UI components, or web APIs can introduce new security vulnerabilities if not reviewed properly. Each patch should be analyzed to make sure it doesn't weaken the browser's existing security measures.

It's important to ensure all new strings or changes to existing strings do not introduce possibilities for injection attacks (such as script injection in web UI components) and comply with any localization requirements. Additionally, the updates in accessibility-related messages should maintain clear and accurate descriptions to avoid any confusion or misuse.