Reduce jobs on release CI..?

Been sat waiting for a tiny release to go through the CI, has made me think we could probably cut down some of the duplicate jobs and speed up a new version being available to use.

• Both releases and main merges are doing storybook:build and storybook:deploy, I assume overwriting each other
• import tests are run on main, which blocks a release being cut. They're then re-run on the release pipeline. Granted these are fast.
• yarn:test too
• same for pre-commit and code_quality, though the former could be argued to be needed given the commit changes done by release-it.