feat: add shopware-cli hub updates command

[Copilot]

Adds a new top-level hub updates command that fetches and displays the latest events from the Shopware Community Hub (https://hub.shopware.com). Hub and Account are separate APIs — no account authentication is required.

New packages

• internal/hub-api/ — standalone HTTP client for the Community Hub public API (GET /api/updates); 30 s timeout, fully context-cancellable, base URL overridable via SHOPWARE_CLI_HUB_URL
• cmd/hub/ — hub command group with updates subcommand

hub updates behaviour

• Groups items by event.event, sorted alphabetically by human-readable label (e.g. hub:release:created → New releases); unknown event types fall back to the raw string
• Renders item titles as OSC 8 clickable hyperlinks in TTY contexts; degrades to text (url) in non-TTY (pipes, CI)
• Handles empty feed and API errors gracefully

$ shopware-cli hub updates

New releases
  • Acme Plugin (https://hub.shopware.com/…)
    2024-06-01

Updated releases
  • Other Plugin (https://hub.shopware.com/…)
    2024-05-30

[somethings (lasomethingsomething)]

Hello Bojan Rajh (@bojanrajh), what's the status of this work? We would need to align on the problem this solves for the user and the UX around it so that we are sure it fits to our roadmap and aligns with team plans.

[Bojan Rajh (bojanrajh)]

somethings (@lasomethingsomething) This was a single-prompt experiment to show some updates from the Hub in CLI. Although it's not directly connected to the project setup or extension management, we could see it as an opt-in/opt-out middleware that runs in non-ci/dev environment.

The CLI itself could already notify the user about new versions, but we can also serve public announcements from Discord and other news from the website (like PaaS, Copilot, Payments and Insider previews). Let's say we would display 1-5 events per week, or 10 per month. I guess the CLI would poll the hub every X requests/minutes/hours, show new events (normalized as {id, title, date, description, url}), and remember when the user was last updated. Simple enough to communicate the most important info in the ecosystem automatically (not with a sub-command), and rare enough to not annoy the user.

Going more into personalization with the Hub, we could display notifications (clubs, academy, comments, ...) which would require more deeper integration for the auth flow. Probably not feasible at the moment, but could get to that in future.

Either way, you can close this and we can either track it in Jira or create an issue in this repo.

[somethings (lasomethingsomething)]

Bojan Rajh (@bojanrajh) Thanks for the information. This is not something I would want to introduce in the CLI without having a serious discussion about the problem this solves, user feedback indicating that they want to see this adopted in the CLI, and an understanding of the value it brings to users Please don't move forward until we've had that discussion. For now, I will close this PR.