Properly support selector lists

[shagkur]

Please ignore the pom.xml changes (we currently need them to fulfill our dependency repository requirements when fetching such custom changed builds). We do this because of having the need changes/fixes available quickly.
The important part is the parser change(s) and the SelectorMember changes i made. You might consider introducing something like CSSRelativeSelector consisting of a combinator field and an array of selector members (:has can hold a list of relative selectors)
And pseudoIs and pseudoWhere did not handle a selector list at all

[phax]

@shagkur can you please provide a little bit of contexts what you want to achieve exactly?

Please also change the pom.xml Group ID back to the default - thx

[shagkur]

As you know there's already an issue filed about pseudoIs not being able to handle a selector list (same issue, after update to 7.0.4 mainstream happend to me). Same applies to pseudoWhere. And for pseudoHas, digging deeper into the spec says it's supporting a list of relative selectors. Your actual implementation only supports one relative selector.
And since you often decide, based on the PR i provide, to implement it a bit differently (according to your standards) to fix the issue after all.
The parser changes were made to solve an issue with CSS url's containing escape characters like \2f (seldomly seen but exist and result in a bug). You can drop the parser changes if you like. I need them for us.