Add tests for color.is-legacy()

[SondraE]

Part of tests for color spaces.
See sass/sass#2831

[nex3]

We should target these color space PRs to separate branch (color-4 would match the branch name in the Dart Sass repo). If we land them on main, it'll break our CI since the actual implementation of the behavior in question isn't finished yet.

[dvdherron]

We should target these color space PRs to separate branch (color-4 would match the branch name in the Dart Sass repo). If we land them on main, it'll break our CI since the actual implementation of the behavior in question isn't finished yet.

@nex3 I don't think we have the right access here to make a new branch. If you create the branch I can re-target these color PRs.

[nex3]

@dvdherron Done 😃. I ended up naming it feature.color-4 so that the CI will run on it

@SondraE You should be able to fix the lint errors by running npm run lint-spec -- --fix. I'm not sure why the Dart Sass tests are running, but they may go away if you run the tests again now that you have [skip dart-sass].

[nex3]

This is passing too few args to rgb(), but it should be passing too few args to is-legacy()

[nex3]

It looks like this is testing both a named argument and a named color—we should have separate tests for each of these cases (see https://github.com/sass/sass-spec/blob/main/STYLE_GUIDE.md#do-test-only-one-thing-per-spec)

[nex3]

Removing [skip dart-sass] since I don't think this will require any code changes in Dart Sass

[nex3]

JS API test failures are unrelated, I'm working on fixing them in #1853