docs: compose logs: add more links for flag descriptions

[thaJeztah]

• follow-up to docs: compose logs: add links for since/until flag descriptions #13806
• relates to docs: container logs: add headers for flags cli#7003

follow-up to 7eeb7de, adding more links now that the CLI reference for docker logs has anchors for them.

What I did

Related issue

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

[thaJeztah]

Actions are failing because some are not pinned;

Getting action download info
Error: The actions actions/checkout@v5, actions/download-artifact@v5, actions/github-script@v8, docker/setup-buildx-action@v4, and docker/bake-action@v7 are not allowed in docker/compose because all actions must be pinned to a full-length commit SHA.

[Copilot]

Pull request overview

This PR updates the docker compose logs reference documentation to link individual flag entries (and their short forms where applicable) directly to the corresponding anchored sections in the upstream docker container logs CLI reference, now that those anchors exist.

Changes:

• Add per-flag details_url anchors for follow, since, tail, and timestamps in the Compose docs YAML.
• Update the generated compose_logs.md options table so flags link to the anchored upstream docker container logs sections.
• Add/update annotation.ExternalURL annotations for the corresponding flags in cmd/compose/logs.go to match the anchored links.

Reviewed changes

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

File	Description
docs/reference/docker_compose_logs.yaml	Adds anchored details_url entries for additional logs flags.
docs/reference/compose_logs.md	Updates generated options table links to point at anchored upstream references (incl. short flags).
cmd/compose/logs.go	Adds/updates annotation.ExternalURL for logs flags to use anchored upstream references.

[docker-agent]

Assessment: 🟢 APPROVE

This PR adds hyperlink annotations (ExternalURL) to four flags (--follow, --timestamps, --tail, and the existing --since/--until) in cmd/compose/logs.go, with corresponding updates to the generated Markdown and YAML reference docs.

All added URL anchors (#follow, #since, #timestamps, #tail) are consistent across the three changed files. No logic errors, formatting issues, or inconsistencies were found in the added lines.

[glours]

@thaJeztah I will open a PR to fix the unpinned versions in workflows right now

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[thaJeztah]

Opened a PR to fix CI;

• gha: update docs-upstream to pin workflows by sha #13834

[glours]

@thaJeztah already merged, you can rebase your PR

[thaJeztah]

Oh! Missed your earlier comment 🙈 will rebase!

[thaJeztah]

Hm... networking issues, or is it changes on our side blocking requests?

#17 [build-base 2/2] RUN --mount=type=cache,target=/go/pkg/mod     --mount=type=cache,target=/root/.cache/go-build     go mod download
#17 18.45 go: github.com/moby/moby/api@v1.54.2: read "https://proxy.golang.org/github.com/moby/moby/api/@v/v1.54.2.zip": stream error: stream ID 747; INTERNAL_ERROR; received from peer
#17 ERROR: process "/bin/sh -c go mod download" did not complete successfully: exit code: 1
------
 > [build-base 2/2] RUN --mount=type=cache,target=/go/pkg/mod     --mount=type=cache,target=/root/.cache/go-build     go mod download:
18.45 go: github.com/moby/moby/api@v1.54.2: read "https://proxy.golang.org/github.com/moby/moby/api/@v/v1.54.2.zip": stream error: stream ID 747; INTERNAL_ERROR; received from peer
------
Dockerfile:52