Make zod peer dependency

[Siegrift]

It should resolve https://github.com/api3dao/ois#make-sure-only-one-zod-version-is-installed

Btw. (if this is not clear), zod can (and should) still be installed as a dev dependency in order for tests to run. But it will not end up in a prod bundle.

[dcroote]

zod can (and should) still be installed as a dev dependency in order for tests to run

But wouldn't this result in the potential for two versions of zod being present?

[Siegrift]

Mhh, how?

[dcroote]

If versions diverged and the peer dependency had say zod@^3.1 and the dev dependency had zod@^4.1, but I guess that's a low risk

[Siegrift]

It doesn't matter even if they diverge. The peer dependencies are not installed automatically (users need to install them manually) so you won't end up with two version used at the same time.

When publishing the package, all dev dependencies are ignored so what we effectively end up with is package without zod library and users need to install it themselves. There could be an issue, if their installed zod version has breaking changes with the one used in OIS but that should happen only if they install a different major version, for which they will get a warning during install (the famous "incorrect peer dependency").

[dcroote]

I'm saying that zod version that this package gets tested against becomes uncoupled from the one installed and used, which would be bad.

[Siegrift]

For reference, we are bundling zod (same way as in OIS currently) in all other repos and it works without issues.