Modify parsers to be AST-based

[asamuzaK]

• Related Ideal jsdom CSS implementation architecture #235
• Fix Replace isValid() with isValidPropertyValue() #236
• Fix Rewrite parsers to be AST based #237
• Fix Use @webref/css #229
• Fix Fix shorthand serialization #228
• Fix Export implemented properties with definitions #241
  • Experimental, subject to change in the future
• Some failing web platform tests now pass:
  • css/css-cascade
    • parsing/all-invalid.html
  • css/css-color
    • parsing/color-invalid-color-function.html
    • parsing/color-invalid-color-layers-function.html
    • parsing/color-invalid-lab.html
    • parsing/color-invalid-named-color.html
    • parsing/color-invalid-relative-color.html
  • css/cssom
    • cssstyledeclaration-csstext-important.html
    • shorthand-serialization.html
      • 12/20 errors -> 4/20 errors
  • css/cssom-view
    • parsing/scroll-behavior-invalid.html

[asamuzaK]

PR ready.
It's a near complete rewrite, but should be non-breaking.

[asamuzaK]

To run test against jsdom locally:

cssstyle:

npm link

cd to jsdom and run:

npm link cssstyle && npm run test

Don't forget to run below against jsdom afterwards.

npm i

[domenic]

I'll merge this, but what should we write in the changelog? It seems like a lot of properties were improved, and some new ones were added? Can we get a list of all of them? Or should we just give up and say "lots of parsing and serialization improvements to all properties"?

[asamuzaK]

No new properties are added.
Regardless of whether they are supported or not, the parser/lexer is now more powerful and accurate than before, so it is able to catch invalid values.
That's why some of the foo-invalid.html tests pass.

Summary of this PR:

• Improved internal processing by switching from regular expression matching to AST-based parsing.
• Improved getter and setter of cssText.
• Improved serialization of border, flex, margin, and padding shorthands.
• Added static propertyList() method to the CSSStyleDeclaration class that lists the supported properties and their data.
  It is intended to eventually replace jsdom's https://github.com/jsdom/jsdom/blob/main/lib/jsdom/living/helpers/style-rules.js#L22, but is still experimental.

[domenic]

• Added static propertyList() method to the CSSStyleDeclaration class that lists the supported properties and their data.

Oh, this seems bad, since it's not in the spec. Can you export it from the module somewhere else instead of putting it on the CSSStyleDeclaration class?

(If we ever created wrappers using webidl2js per #235, then it wouldn't matter, but right now jsdom directly exposes cssstyle's CSSStyleDeclaration, so it needs to not have extra methods outside of the spec.)

[asamuzaK]

It's fine with me to expose propertyList() separately from the CSSStyleDeclaration class, but if that's the case, wouldn't it be better to create a wrapper as soon as possible?
Currently, CSSStyleDeclaration accepts arguments that are not in the spec, i.e. constructor(onChangeCallback, opt).