Refactor to remove style-search

We’ve been gradually moving away from style-search in favour of using the value parser.

This is an umbrella issue to track that migration.

Rules:

• function-calc-no-unspaced-operator
• selector-pseudo-element-colon-notation
• value-no-vendor-prefix

Utils:

• rangeContextNodeParser
• functionArgumentsSearch

Stylistic rules and utils (no need to update as will eventually be deprecated and removed):

• function-whitespace-after
• indentation
• max-empty-lines
• max-line-length
• no-eol-whitespace
• no-extra-semicolons
• selector-attribute-brackets-space-inside
• selector-list-comma-newline-after

Utils:

• declarationBangSpaceChecker
• findMediaOperator
• mediaFeatureColonSpaceChecker
• mediaQueryListCommaWhitespaceChecker
• selectorAttributeOperatorSpaceChecker
• selectorListCommaWhitespaceChecker
• valueListCommaWhitespaceChecker

When adding an option or fixing a bug with one of these rules (or a rule that uses a utility using search-search), consider refactoring it to use the value parser.

Ref: https://github.com/stylelint/stylelint/pull/5496#discussion_r694494678

[jeddy3]

Can we use the value parser as a stepping stone to a parser that understands this construct?

The value parser will parse this a series of word nodes. We can then spot the operator word nodes.

[jeddy3]

I’ve updated the task list above to ignore stylistic rules and utils.

It leaves us with only two rules and two utils left to migrate to a parser.

I think rangeContextNodeParser is a good candidate to migrate to a future-facing parser like SWC. Having said that, all the rules can be migrated to postcss-based parsers as a stepping stone away from stylesearch.