feat: add structured Pino logging to starter node template

[zeroknowledge0x]

Closes #997

Summary

Replaces all console.log/console.error calls with structured Pino logger for consistent, JSON-formatted log output in the bridge-starter-node template.

Changes

• Add pino and pino-pretty as dependencies
• Create src/config/logger.ts — centralized logger with dev (colorized) and production (JSON) modes
• Add src/middleware/requestLogger.ts — logs method, URL, status code, and duration for every request
• Update webhook.ts — structured logging with event type context
• Update bridge.ts — structured error logging with API response context
• Update app.ts — wire up request logger middleware

Testing

• Logger outputs JSON in production mode, colorized in dev
• Request logger captures all HTTP requests with timing
• All console.log/console.error replaced with typed pino methods (info, warn, error)

[sublime247]

@unsiqasik was this assigned to you ??

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	JSON Web Token	45e3b17	src/utils/tests/scrub.test.ts	View secret
-	-	Bearer Token	45e3b17	src/utils/tests/scrub.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}