Add exclusions allowing jest and vite configs to import dev dependencies and remove from generated package.json files

[luxaritas]

The only reason I have these packages listed as dev dependencies in generated packages is to avoid the linting issue, which we should really just solve in our eslint config

[luxaritas]

This is actually not just an issue of allowing dev dependencies (the vite config already did this), but also specifying the package directory properly

[luxaritas]

I'm not sure if there is a clean way to do this, as we don't necessarily know ahead of time how many directories deep our package is from the workspace root. Probably this is better handled by eslint-plugin-import, and there is an open issue for that: import-js/eslint-plugin-import#1913

[luxaritas]

Submitted PR import-js/eslint-plugin-import#2481. No idea how long it'll take to merge plus get included in a release, in the meantime we could try to use a workaround suggested in the issue or something similar.

[luxaritas]

Additional note per #40, I think we want to limit devDependencies to only be in the root package.json (and all regular dependencies to be specified within the package itself), so that makes this a bit easier