Epic: Composed end-to-end release workflow

[stephane-segning]

Epic: Composed end-to-end release workflow

README.md's own "Roadmap" section names exactly one thing:

An optional workflow_call that composes setup -> version-stamp -> build -> release-cut
-> submit -> publish end-to-end, so a consumer calls one thing.

Today a consumer (e.g. vaam-store/mobile's own CI) wires each of these steps
individually. This epic turns that README roadmap line into a tracked issue — it wasn't
one before this pass.

Stories

• Not yet filed — will be filed once there's a concrete design for the composed
  workflow_call's inputs/outputs (which sub-actions it wraps, how per-platform
  variance — Android vs iOS — is expressed). Filing a placeholder issue with no design
  would just be restating this epic's body; add the story once that design exists.

Source of truth

README.md, "Roadmap" section (quoted above verbatim).