Fix build dependency issue with settings and extension pages resources

[petemill]

Resolves brave/brave-browser#13567

This should be uplifted to wherever chromium 88 is

Submitter Checklist:

• There is a ticket for my issue.
• Used Github auto-closing keywords in the commit message.
• Wrote a good PR/commit description
• 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).
• Requested a security/privacy review as needed.

Reviewer Checklist:

• 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:

[bridiver]

do we still need the other patch in this file? https://github.com/brave/brave-core/pull/7599/files#diff-5606dbee6795afa01ac32eebfe4d4cfc97f19d928fc34fac419a49599530a6adR17

[bsclifton]

I believe we do need the other patch as line 17 in patches/chrome-browser-resources-settings-BUILD.gn.patch is used for our settings customizations. This is a different page
cc: @petemill

[petemill]

@bridiver I believe we do as they are different sets of files used at different steps of the build, and we can't simply add these new ones to that other brave target because it still won't guarantee it will happen in the right order, and we can't add the deps only in the other place as that's inside a optimize_webui conditional.

[petemill]

@bsclifton same applies to both settings and extensions. They both need 2 patches as far as I can tell so far.

[bridiver]

approving to unbreak the build, but I'd like to follow-up and make sure we have only the patches we need and not any extra

[petemill]

re-building macos

[bsclifton]

++

[mkarolin]

++

[petemill]

Merging because CI is only being problematic for macOS and that's build-instance related, not PR-related. We've tested ourselves with macOS, all the other platforms have built ok with CI and this is only a dep addition aimed to fix CI.