[Feature]: Build pipeline improvements

### Feature Request

The build pipeline for PRs could be improved.

- [ ] support PR types (GitHub's default triggers for PRs have problems) adding types fixes some of those
- [ ] support concurrency groups (i.e. if a PR receives a new commit, any running builds on that PR should cancel and start over with latest changes)
- [ ] support "yarn install" caching to speed up builds (optional)
- [ ] run "yarn build", "yarn test" and "yarn lint" as parallel tasks for better performance (requires caching)
- [ ] fail a PR if "yarn lint" finds issues
- [ ] add prettier support to "yarn lint"
- [ ] skip "yarn build" if PR is in draft mode, but run "yarn test/lint" (this is opinionated)

Future pipeline improvements (to be discussed)

- add test coverage reports to PR comments automatically
- add GitHub hooks that automatically lint/prettier code when pushing changes (to ensure code styling standards)

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

The issue names no workflow files, so start by locating the GitHub PR build workflow and its current triggers and jobs. Review how yarn build, yarn test, and yarn lint are run, then implement a clearly selected subset of the checklist; done means the chosen checks behave as described and PR validation passes.

Written by the indexing model from the issue text.