Split CI into discrete jobs

[sarayourfriend]

Fixes

Fixes #890 by @sarayourfriend

Description

Adds a new setup-node-env composite action to make node and pnpm installation more DRY.

Splits unit tests, e2e test, storybook build, nuxt build, linting, i18n verification, and type checking into discrete jobs in the CI so that they all run at the same time.

Testing Instructions

Check that the CI is running as expected compared to the behavior described in the yaml files.

Checklist

• My pull request has a descriptive title (not a vague title like Update index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• [N/A] I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

We moved the API repostory in the opposite direction, moving all separate jobs into a comprehensive CI + CD workflow (example run) that builds images, lints, runs tests, publishes images to GHCR and also deploys docs to GH pages. I believe that a comprehensive workflow is better than many separate ones because

• it's easier to share artifacts and environments
• you can visualise the entire process from the Actions diagram
• it's also concurrent (jobs that don't depend on each other will run in parallel even in the same workflow)

[sarayourfriend]

@dhruvkb Gotcha. I mostly just wanted to split each of the discrete tasks into their own jobs. I've pushed them into a single workflow now.

[sarayourfriend]

One disadvantage to putting everything into the same workflow is that you can't re-run discrete parts of it, you have to re-run every single check. I guess it doesn't cost anything to us really, it just always bugs me!

[obulat]

Nice addition!

[zackkrida]

LGTM. One non-blocking question, would there be any benefit to checking lint errors prior to types? I think it's probably even better the way it is but i thought of the question and thought I'd pose it.