Improve our Sass workflow to check for compilation of variables and functions with LibSass and Ruby Sass

[romaricpascal]

What

Improve our Sass workflow to verify that Libsass and Ruby Sass correctly transform all the Sass variables and functions in our code.

Why

Our Sass code can still be imported with Libsass and Ruby Sass (as we've yet to move to Sass module system). However these older versions do not transform some newer syntaxes supported by dart Sass, outputting invalid CSS.

Who needs to work on this

Developers

Who needs to review this

Developers

Done when

• Our Sass workflow checks for the presence of Sass variables in the built ouput
• Our Sass workflow checks for the presence of function calls starting with govuk- in the built output.

[romaricpascal]

A possible way to achieve this could be to run a custom Stylelint plugin with two rules:

• one failing at the presence of a Sass variable
• one failing at the presence of a function starting with govuk- (as there may be legitimate calls to CSS functions and we don't want to keep an eye on all the functions in CSS as of today or introduced in the future).

[romaricpascal]

#4784 nicely finds the Sass variables using grep. If we can use grep to match the function calls as well, that would be ace. This may require us to use the -E or -P flag for more complex regexp.

[colinrotherham]

Bit late now, but this would do it:

! grep --regexp "\$govuk-" --regexp "govuk\-\([a-z0-9-]\+\)(" .tmp/all.css