List services never deployed to production

[lesnik512]

Feedback from the first GitLab trial: a service with no production deployment yet (dialogs-data-egress) was missing from the page, so its first release could not be picked.

• With no successful deployment to the production environment, collect now walks the default branch from its head down to the first commit, capped by RELEASE_SCOPE_MAX_COMMITS as usual, instead of stopping with no rows. The warning stays and says the rows run from the first commit.
• Its candidates get compare_url pointing at the tag's commit history (/-/commits/<tag>), since there is no production to compare from.
• The page lists a service when it has a production deployment, rows, or an error. A never-deployed service shows not in production → <tag>, and its Compare and Release post lines read commits to <tag>.

No report schema change: compare_url stays a string and the page tells a never-deployed service apart by its missing production environment. Consumers that assumed rows imply a production deployment should check environments; the skill doc says so.

Jira mode needs nothing extra: scoping works on the same walk.