feat : check for missing fragment elements

[hirasso]

Description

Introduces a check while matching fragment rules, that validates if any of the selectors in rule.containers doesn't return a match in the current document. If so, the rule will be skipped for the current visit.

Makes the PR #47 unnecessary for the use case I'm facing right now. I'd like to keep the rule API surface as small as possible until we stumble on a use case where we really need to expand it. We can keep the rule.if PR open and in sync, should we need it sometime.

Checks

• [x] The PR is submitted to the master branch
• [x] The code was linted before pushing (npm run lint)
• [x] The documentation was updated as required

[daun]

Is this breaking? Do we care?

[hirasso]

I'd say it's not breaking. IMO it was almost a bug as it was before.

[hirasso]

Sorry, again please 👔