Make pino a peer dependency

[satazor]

The main reason for pino to be changed to a peer dependency, is to ensure that pino installed in the project has the same version as the one from this library. This is particularly important if you use setRootLogger for advanced cases where destination, and other pino static functions are used during that process:

import { destination, pino } from 'pino';

const stream = destination({ dest: 2 });
const options = {  errorKey: 'error' };

setRootLogger(pino(options, stream));

Dependency management:

• Changed pino from a direct dependency to a peer dependency in package.json, allowing users to bring their own compatible version (^9 || ^10).
• Added pino to devDependencies for local development and testing.

Documentation:

• Updated the installation command in README.md to instruct users to install both @uphold/debino and pino.

[Copilot]

Pull request overview

This PR changes how pino is consumed by @uphold/debino by moving it from a direct runtime dependency to a peer dependency, and updates docs/lockfiles accordingly so consuming applications explicitly install a compatible pino.

Changes:

• Move pino from dependencies to peerDependencies (^9 || ^10) and add it to devDependencies for local development/testing.
• Update README installation instructions to include installing pino.
• Regenerate package-lock.json to reflect the dependency graph changes.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 3 comments.

File	Description
README.md	Updates install command to include pino.
package.json	Makes pino a peer dependency and adds it as a dev dependency.
package-lock.json	Updates lockfile to reflect pino moving to dev + peer deps.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.