Refactor value parsing to use a simpler algorithm

[romainmenke]

Which issue, if any, is this issue related to?

None, it's a minor code quality fix that I noticed while working on a different issue.

Is there anything in the PR that needs further explanation?

This isn't a user facing change, so I am omitting a changelog entry.

---

parseCommaSeparatedListOfComponentValues :

• list of lists of component values
• split by comma
• doesn't include the comma as a component value
• useful for :
  • media query lists
  • selectors
  • function params (rgb(0, 0, 0))

parseListOfComponentValues :

• list of component values
• no splits
• does include the comma as a TokenNode
• useful for anything

This distinction is important when writing specialized parsers (like the media query parser) but it isn't relevant when validating component values.

Using parseListOfComponentValues results in simpler, cleaner code.

---

The diffs appear large because the indent changed.

Actual diff :

- parseCommaSeparatedListOfComponentValues(tokenize({ css: value }))
- 	.flatMap((x) => x)
+ parseListOfComponentValues(tokenize({ css: value }))
	.forEach((componentValue) => {

[changeset-bot]

⚠️ No Changeset found

Latest commit: faccd83

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ybiquitous]

LGTM. Thanks!