ci: release with pnpm publish instead of action

[mcous]

Overview

This stack of PRs updates our common JS configs over to their 1.0.0 versions. The main difference between the versions so far and v1 is that (thanks to the ESLint v9 update) the various plugins and configs that we stitch together will be pulled in automatically as dependencies - simplifying setup by removing most required peer dependencies.

1. 🌿 ci: release with pnpm publish instead of action #48
2. feat(prettier-config)!: split configs and use direct dependencies #49
3. feat(eslint-config)!: split config packages #50
4. TODO: Update ESLint packages to use ESLint v9 and flat configs

Change log

This PR gets ready for this change by:

• Switching the publish job to pnpm publish --recursive, allowing us to use workspace dependencies properly across projects
• Switching our TSConfig to use project references, for the same reason
• Updating deps to avoid cluttering future PRs

Review requests

Nothing in particular here as long as CI is green

[ehhong]

not the most familiar with this workflow, so going to allow others to approve

[zaporter]

projectService is neat. Thanks for doing this!

[katiepeters]

😎