feat: make hook hint deep links clickable using OSC 8 terminal hyperlinks

[glours]

What I did

Wrap the docker-desktop://dashboard/logs URL in OSC 8 escape sequences with underline styling so it appears as a clickable link in supported terminals. Respects NO_COLOR and COMPOSE_ANSI=never to suppress escapes.

Related issue
N/A

(not mandatory) A picture of a cute animal, if possible in relation to what you did

[Copilot]

Pull request overview

This PR updates the Compose hook “next steps” hint to render the Docker Desktop logs deep link as a clickable OSC 8 terminal hyperlink (with underline styling), while suppressing escape sequences when ANSI output is disabled via NO_COLOR or COMPOSE_ANSI=never.

Changes:

• Added Osc8Link helper to generate OSC 8 hyperlinks when ANSI is enabled.
• Updated hook hint templates to use hyperlink-wrapped deep links, gated by env-based ANSI suppression.
• Added unit tests for OSC 8 link formatting and hook output under ANSI-enabled/disabled conditions.

Reviewed changes

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

File	Description
cmd/formatter/ansi.go	Adds OSC 8 hyperlink helper and improves lenAnsi documentation.
cmd/formatter/ansi_test.go	Adds tests validating OSC 8 hyperlink output and ANSI-disabled behavior.
cmd/compose/hooks.go	Converts hint templates to functions and wraps the deep link using OSC 8 when allowed.
cmd/compose/hooks_test.go	Updates existing expectations and adds tests for OSC 8 presence/absence based on env.

---

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

[afurm]

The template string field on hookHint was changed to template func() string, and callers switched to hint.template() — this shifts from a static string to a lazy evaluation. The original design appeared to call enc.Encode once per hook invocation, so lazy evaluation should be fine here. However, if hookHint is ever used in a way where the template is inspected rather than rendered (e.g., log output, JSON marshaling of the struct itself), the function would not serialize correctly. Does any code path marshal hookHint directly to JSON?