Feature Request: config dependencies

[bgotink]

Similar to https://pnpm.io/config-dependencies

A way to share configuration would be greatly beneficial to orgs, ensuring defaults can be applied consistently.
For example, every repo in our org

• uses logFilters to turn missing and invalid peer deps into errors instead of warnings
• uses nodeLinker: node-modules
• configures supportedArchitectures

We would love to extend this and start setting npmMinimalAgeGate, preferReuse, … but the fact that we'd have to update this in hundreds of repositories maintained by dozens of teams has kept us back.
If config could be published as an npm package, we'd be able to reduce this to a single change + a bunch of version updates, leading to more consistency and fewer mistakes.

This will be extra useful as zpm supports the catalog: protocol, as being able to share catalogs across repositories would be a huge improvement.