⬆️ Bump Honeydiff to 0.11 (#300)

## Why

Honeydiff 0.11.0 is published with release-package fixes and updated
comparison behavior, so the CLI should test and package against the same
version as the app runtime. This keeps local TDD comparison behavior
aligned with the current Honeydiff release.

## Approach

The CLI dependency moves to ^0.11.0 through pnpm, and the workspace
keeps the release-age policy intact by swapping the existing first-party
Honeydiff exception from 0.10.3 to 0.11.0. That avoids a broad
supply-chain bypass while still allowing this freshly published
first-party package.

## Evidence

The updated native package imports successfully, CLI linting passes,
type assertions pass, and focused command/TDD comparison tests continue
to pass with the new dependency.

## Risk

The release-age exception is intentionally version-specific. It should
be revisited on the next Honeydiff bump rather than expanded to the
whole package scope.

Author: Robdel12

package.json

@@ -94,7 +94,7 @@
   },
   "dependencies": {
     "@vizzly-testing/bear-den": "0.1.2",
-    "@vizzly-testing/honeydiff": "^0.10.3",
+    "@vizzly-testing/honeydiff": "^0.11.0",
     "ansis": "^4.2.0",
     "commander": "^14.0.0",
     "cosmiconfig": "^9.0.0",

pnpm-lock.yaml

@@ -15,7 +15,7 @@ minimumReleaseAgeStrict: true
 minimumReleaseAgeIgnoreMissingTime: false
 minimumReleaseAgeExclude:
   - '@vizzly-testing/bear-den@0.1.2'
-  - '@vizzly-testing/honeydiff@0.10.3'
+  - '@vizzly-testing/honeydiff@0.11.0'
 onlyBuiltDependencies:
   - canvas
   - esbuild