Bump less-cache to 2.0.1

[savetheclocktower]

Identify the Bug

Fixes the bug that was addressed in less-cache#6.

Description of the Change

Inline JavaScript (within backticks) will once again be tolerated within certain LESS constructs. This is a feature I was using so that I could write

.s('string.quoted.double', { color: green; });

instead of

.syntax--string.syntax--quoted.syntax--double {
  color: green;
}

Less.js has deprecated this behavior, but we haven’t, and it’s good not to break stuff.

Alternate Designs

There is an alternative way of pulling this off with @plugin rules, but it only works in Less v4, and there’s no simple way to offer up the right solution for the user’s Pulsar version, so I’ll hold off on adopting that approach in my syntax theme until I’m certain it won’t break for the entirely fictional other people who are also using vibrant-ink-redux as their syntax theme.

Possible Drawbacks

I can’t think of any. This is no less secure than what we were already doing, and I don’t think it’s a security problem at all, since the JS inside a less file is ultimately no less sandboxed than the JS we allow a package to run otherwise.

Verification Process

Wrote a unit test in less-cache to demonstrate the fix. If CI passes, we should be good.

Release Notes

Restored ability for less files in packages to use inline JavaScript inside backticks

[confused-Techie]

LGTM! Simple enough change, bumped exactly what needs to be. Only thing better is getting the yarn lock file synced so Renovate doesn't freak out, but really not an issue.

Approving since the only CI failure (ARM Linux) is failing yet again with strange SSL issues, which we know is due to CI issues. So hoping we can get those successful after a run or two lets get this merged.

[confused-Techie]

Thanks for adding that last bit I mentioned! After a few reruns I'm still not getting ARM to be happy, but the failure looks to be totally caused by CI issues. So lets go ahead and merge this