[Story]: Re-point delivery at the console

## Story Statement

As a developer and operator of converse-frontends,
I want the release pipeline (Helm chart, image workflow, Storybook publishing) pointed at
`apps/console` instead of the retired Expo app,
so that the repo ships a real, deployable artifact again and `packages/ui-web`'s Storybook is
actually published.

## Real Intent

#258 disabled automatic image builds as a stopgap because they still targeted the Expo app. That
stopgap only makes sense if it is followed by re-pointing delivery at the surface that actually
matters now — the console. Leaving it as-is indefinitely means the repo ships nothing, and
`packages/ui-web` — the design system the console actually uses — has never once had its Storybook
published, because `storybook-pages.yml` is still hardcoded to the old package's path.

## Background and Context

`charts/converse-frontend` and `docker-image.yml` still build/deploy the Expo app; `docker-image.yml`
is currently `workflow_dispatch`-only per #258. `storybook-pages.yml`'s path filter is hardcoded to
`packages/ui/**`, so `packages/ui-web`'s Storybook — despite being live and in active use by the
console workstream — has never deployed.

## Source of truth (links)

ADR 0009, Decision 1 and Follow-up 7: https://github.com/ADORSYS-GIS/converse-frontends/blob/main/docs/adr/0009-nextjs-console-replacement.md
#258 (image builds disabled, `workflow_dispatch` only): https://github.com/ADORSYS-GIS/converse-frontends/pull/258

## Acceptance Criteria

### Functional
- [ ] Given `docker-image.yml` and `charts/converse-frontend` after this story merges, when a
release is triggered, then a `apps/console` image is built and the GitOps chain resolves it.
- [ ] Given `storybook-pages.yml` after this story merges, when `packages/ui-web` changes, then its
Storybook publishes.

### Negative / Edge Cases
- [ ] Given the re-pointed `docker-image.yml`, when it is first exercised, then the trigger is
deliberate (manual/tagged), not silently automatic, so a bad first build cannot ship
unattended.

### Non-Functional
- [ ] The GitOps chain (private OCI chart/image → ai-helm `converse-ui` ArgoCD app → home-os
cluster) resolves the re-pointed chart/image without manual patching.

## Out of Scope

Deleting the Expo app/`packages/ui` itself — tracked in Story 5.1. Deciding *when* to cut a
production release beyond making the pipeline capable of it.

## Dependencies and Blockers

Depends on Story 5.1's deletion for the pipeline change to make sense as a permanent state, but is
not strictly blocked on it — the Helm chart/workflow retarget and the Storybook filter widening can
land independently since they only change what CI builds/publishes, not what exists in the repo.

## Assumptions

- The GitOps chain documented for this repo (private OCI chart/image → ai-helm `converse-ui`
ArgoCD app → home-os cluster) is still the correct target — confirm with the delivery owner
before merging.

## Implementation Notes

Re-enable `docker-image.yml` against `apps/console`'s existing Next.js build output; update
`charts/converse-frontend` to match the console's runtime config (no more nginx/`envsubst`, per
Story 5.1). Widen `storybook-pages.yml`'s path filter to include `packages/ui-web/**`. Guidance
only — the implementing engineer may find a safer sequencing.

## Test Expectations

- A manually-triggered `docker-image.yml` run producing a console image, verified against the
ai-helm ArgoCD app.
- A `packages/ui-web` change confirmed to trigger `storybook-pages.yml` and publish.

## Verification evidence

To be filled in by the implementing engineer at delivery time: workflow run links, published
Storybook URL, ArgoCD sync confirmation.

## Human accountable owner

@stephane-segning

## AI Usage Declaration

- Ticket decomposition

## Human verification completed

- [ ] I checked the story against the source of truth
- [ ] I confirmed the acceptance criteria
- [ ] I reviewed the implementation approach
- [ ] I verified generated code manually
- [ ] I verified generated tests manually
- [ ] I removed or corrected unsupported AI claims
- [ ] I am the accountable owner and accept responsibility for this story.