Fix crash when invalid args for library polished's functions

[lonyele]

Issue: Fixes #6855, #6756, #6135

What I did

Problem

When using some functions from polished such as lighten(...), darken(...), its arguments that can't be converted to RGB throws the error

Commit that possibly introduced this bug

Implementation

• Check if arguments of those functions are valid(gradient, css variable, calc etc...)
• Since it is used on different places, I put it into util.js from @storybook/theming (I couldn't find the place to put some util/shared functionalities across packages. If it doesn't look ok, please let me know where to put these kinds of functions)

How to test

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps? No
• Does this need an update to the documentation? No

[vercel]

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

Latest deployment for this branch: https://monorepo-git-fork-lonyele-fix-linear-gradient-crash.storybook.now.sh

[shilman]

Nice!!! Can you call these lighten and darken for consistency's sake?

[lonyele]

Yeap, I applied your feedbacks~

[ndelangen]

Thanks for contributing @lonyele 🎉

[lonyele]

Oh, I'm working on this one, please wait for a while

[lonyele]

Hm... I'm not sure if the snapshot should be updated(https://circleci.com/gh/storybookjs/storybook/130895?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link) Help is needed here...

I found from library polished that if anything goes wrong, it throws new PolishedError(...) I feel like this is a small hot fix, but it is a not bad start to be safe from polished's exception. Potentially any user inputs that are being passed to polished can go wrong. I'm not sure if it should be refactored since there are a lot and it is only for the few cases, but if it is needed then any custom logic can be added easily here

btw after fixing crash, its values affect normally like this.

To fix these things, I think theming needs to handle more specific parts(maybe relates to)

[lonyele]

sorry mistake

[ndelangen]

@lonyele run:

yarn test --core --update

Then commit the changes generated, to fix the snapshots.

---

I can do it for you, just let me know.

[lonyele]

@ndelangen Hm... my changes of chromatic looks very wrong. I'll investigate this

[ndelangen]

Indeed, I denied the changes that seems wrong.

[lonyele]

@ndelangen oh god... one of the most stupid mistake I've made in few months. I hung my head in shame...
Just a side note, because of this try/catch tests were all passed even with this stupid mistake.

done