Reuse procedural_filters.ts for ios

[atuchin-m]

Resolves

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

[github-actions]

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

Description

This PR introduces changes to the cosmetic filters functionality in the Brave browser, particularly for iOS. It moves the content cosmetic filters script from iOS-specific files to a shared location, making it available for both iOS and non-iOS platforms. The PR also updates the build configurations and script handling to accommodate these changes.

Changes

Changes

1. components/cosmetic_filters/resources/data/BUILD.gn:

   • Added conditional compilation for iOS, introducing a new entry point for content_cosmetic_ios.js.

2. components/cosmetic_filters/resources/data/content_cosmetic_ios.js:

   • Moved and modified the content of SelectorsPollerScript.js to this new file.
   • Updated copyright year and removed iOS-specific wrapper.
   • Imported applyCompiledSelector and compileProceduralSelector from procedural_filters.

3. components/resources/BUILD.gn:

   • Added dependency on cosmetic filters resources for all platforms.

4. ios/brave-ios/Package.swift:

   • Removed references to SelectorsPollerScript.js and ProceduralFilters.js.

5. ios/brave-ios/Sources/Brave/Frontend/Browser/User Scripts/ScriptFactory.swift:

   • Updated script generation to use AdblockService.cosmeticFiltersScript().

6. Removed ios/brave-ios/Sources/Brave/Frontend/UserContent/UserScripts/Scripts_Dynamic/Scripts/Sandboxed/ProceduralFilters.js.

7. ios/browser/api/brave_shields/BUILD.gn:

   • Added dependencies on cosmetic filters and static resources.

8. ios/browser/api/brave_shields/adblock_service.h and adblock_service.mm:

   • Added a new class method cosmeticFiltersScript to retrieve the cosmetic filters script.

Possible Issues

1. The removal of iOS-specific files and integration into a shared component might lead to unexpected behavior if there are iOS-specific requirements not accounted for in the shared implementation.
2. The change in how the cosmetic filters script is loaded and executed on iOS might affect performance or functionality if not thoroughly tested.

Security Hotspots

No significant security hotspots were identified in this change. However, as with any change involving content scripts and filters, thorough testing should be done to ensure that the new implementation doesn't introduce any vulnerabilities or unintended behavior in content blocking.