needed infra maintainence

This is the setup that I've used on my latest project, https://github.com/universal-ember/ember-primitives
- publint -- verifies that your package (tgz) is correct
- are the type wrong -- lint that verifies that published types are correct, and package.json agrees
- turbo
- to orchestrate various scripts (are-the-type-wrong needs npm [pack](https://github.com/universal-ember/ember-primitives/blob/main/ember-primitives/package.json#L28) first, for [example](https://github.com/universal-ember/ember-primitives/blob/main/turbo.json#L117)
- v1 level DX in v2 addon monorepo (partially via `sync-dependencies-meta-injected` (which often required when v2 addons need peers to resolve correctly in their test apps))
- cached job running (saves the environment)


This should probably be applied to all the v2 addons, tbh.
It's a lot to set up right now, but I think with a couple more package additions and lints, it can be fairly easy to maintain -- just have to write those lints

Start by reviewing the repository’s existing v2 addon package configuration and scripts, then compare them with the referenced package.json and turbo.json examples. The issue does not identify target files, required lints, or acceptance criteria, so define the scope and what consistent maintenance setup across v2 addons would mean before changing anything.

Written by the indexing model from the issue text.