Recent versions of Chromium support :has() CSS selector, AG Content Blocker should support it

### Prerequisites

Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.**

- [x] I am running the latest version
- [x] I checked the documentation and found no answer
- [x] I checked to make sure that this issue has not already been filed

### Problem Description

Recent versions of Chromium support :has() CSS selector, AG Content Blocker supports it as well.
Btw, AG Content Blocker recognizes only this syntax:
`example.org##body > div > p:has(>a)`
and it works like a charm. However, it should recognize this syntax too:
`example.org#?#body > div > p:-abp-has(>a)`
`example.org#?#body > div > p:has(>a)`

### Proposed Solution

1) Change AG Content Blocker behavior in order to recognize the correct syntax;
2) Update android-content-blocker/filters/*.txt lists adding AG filters that use :has() css selector .

### Alternatives Considered

Update android-content-blocker/filters/*.txt lists adding AG filters that use :has() css selector, using syntax recognized by Samsung Internet.

### Additional Information

Android 13 - One UI 5
Samsung Internet 22.0.6.9
AG Content Blocker 2.7.2

Start with android-content-blocker/filters/*.txt and existing :has() rules, then trace where the #?# and :has() syntax is handled. Done means AG Content Blocker recognizes both proposed forms and the relevant filter lists include supported :has() rules; verify on the stated Samsung Internet and Android setup.

Vom Indexierungsmodell aus dem Issue-Text verfasst.