replace dchecks in EnableFilterList with conditional early returns

[antonok-edm]

Resolves brave/brave-browser#14123
(See also brave/brave-browser#31561)

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

See brave/brave-browser#14123 - there should be no crash

[goodov]

what about this one?

[atuchin-m]

LGTM with a nit about DCHECK(catalog_entry != filter_list_catalog_.end());

[kjozwiak]

Verification PASSED on Pixel 6 running Android 14 using the following build(s):

Brave | 1.59.35 Chromium: 116.0.5845.96 (Official Build) canary (64-bit)
--- | ---
Revision | ee59f36b912d22844907d1339383d3c7ca7bb0d4
OS | Android 14; Build/UPB5.230623.003; 34; REL

I couldn't reproduce the original issue/crash using 1.59.26 Chromium: 116.0.5845.96 following the STR/Cases outlined via brave/brave-browser#14123 (comment). I went through the same STR/Cases using 1.59.35 Chromium: 116.0.5845.96 which includes the following PR and ensured that there was no crashes/issues as per the following:

screen-20230821-174600.mp4