Add syrupy snapshot tests for bump lockfile messages and publish stale-lockfile errors

[coderabbitai]

Background

Raised during review of PR #75 (refresh stale Cargo lockfiles before publish preflight).

Problem

PR #75 introduced new text-based CLI output for lockfile operations:

• lading bump now renders lockfile paths in its result message with a (lockfile) suffix
• lading publish now emits a multi-line stale-lockfile error including repair commands

Both outputs are currently verified only by substring matching. This allows unintentional formatting regressions to go undetected.

Resolution

Add syrupy snapshot tests covering:

• Bump result message with a root Cargo.lock (lockfile suffix)
• Bump result message with a nested tests/ui_lints/Cargo.lock
• Publish PublishPreflightError message for a single stale lockfile
• Publish PublishPreflightError message for multiple stale lockfiles

References

• PR: Refresh stale Cargo lockfiles before publish preflight (#61) #75
• Requested by: @leynos

[coderabbitai]

🔗 Related PRs

leynos/mdtablefix#276 - Cli matrix testing [merged]
leynos/axinite#175 - Flatten build tool override resolution (#39) [merged]
leynos/tei-rapporteur#79 - Use named validation BDD scenarios (#34) [merged]
#70 - Interleave live publish packaging (#59) [merged]
leynos/repovec-appliance#37 - Serialize qdrant key provisioning (#29) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!