fix: remove duplicate bippy lockfile entry

[tatoalo]

Problem

pnpm install --frozen-lockfile fails because pnpm-lock.yaml contains the bippy@0.5.43 mapping twice. The duplicate was introduced when #3392 was merged.

Why: Restore dependency installation in CI by making the lockfile valid YAML again.

Changes

Removed the duplicate bippy@0.5.43 package mapping while retaining the canonical peer dependency metadata.

How did you test this?

• pnpm install --frozen-lockfile --ignore-scripts
• Verified exactly one bippy@0.5.43 package mapping remains.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[trunk-io]

😎 Merged manually by @tatoalo - details.

[stamphog]

The change touches pnpm-lock.yaml, which is on the dependency/toolchain deny-list and requires human review regardless of how trivial the edit is.