fix: Incorrect parsing of functional pseudo class css selector

[billyvg]

This fixes a parsing issue of CSS selectors that use a functional pseudo class with multiple arguments.

For example,

.foo:has(button,div) {}

Would get parsed as 2 selectors: .foo:has(button and div) - this results in an invalid stylesheet and looks like the replay is broken.

[billyvg]

The logic is as follows:

• Iterate through the split selectors and look for the first selector with an opening parenthesis
• If opening paren is found, look through the rest of the selectors to look for a matching number of closing parentheses
  • If closing paren is found, merge together all selectors between the opening and closing
    • Move iterator index to the next selector and continue
  • If no closing paren is found, assume that selectors were correctly split

[c298lee]

Tests are passing and comment on logic of the code makes sense

[ryan953]

I'm trying to break it 🗡️

edit: i will check it out, and run these test suggestions to see what happens. Maybe think of more tests
edit2: huzzah! 2/3 of my suggestions break it. The first and the last .bar:has(div, input:is(:disabled), button) {} and .bar:has(input:is(:disabled),.foo,button:is(:disabled)), .foo:has(input, button), .baz, {}

[billyvg]

@ryan953 good test cases! I've updated to track the net unbalanced across each selector - however this does add another regex