Create automated release.yml CI workflow

> [!IMPORTANT]
> Link the implementing PR to this issue by including `Closes #`
> in the PR description or commit message.

### What

Create `.github/workflows/release.yml` — a `workflow_dispatch` workflow that
automates the Time module release pipeline:

- Accepts a `tag` input (e.g. `v0.8.0`)
- Runs `build-linux.yml` and `build-qnx.yml` as reusable workflows to verify the
release commit builds cleanly on all platforms
- Collects the code coverage artifact
- Generates a draft GitHub Release populated from `.github/RELEASE_TEMPLATE.md`
and the latest `docs/release_notes/release_note_v_*.rst`

Based on the pattern established in `eclipse-score/lifecycle/.github/workflows/release.yml`.

### Acceptance Criteria

- [ ] `.github/workflows/release.yml` exists and is triggered by `workflow_dispatch` with a `tag` input
- [ ] Workflow runs Linux + QNX builds and fails the release if either fails
- [ ] Coverage artifact is downloaded and attached to the GitHub Release
- [ ] Draft release is created (not published) so a maintainer can review and publish
- [ ] `.github/RELEASE_TEMPLATE.md` is created with standard release body structure
- [ ] Release notes are picked up from `docs/release_notes/release_note_v_*.rst` if present

### References

- Release process definition: #101
- Parent epic: #108
- Lifecycle reference implementation: `eclipse-score/lifecycle/.github/workflows/release.yml`

Start with the referenced eclipse-score/lifecycle/.github/workflows/release.yml, then inspect .github/workflows/build-linux.yml, .github/workflows/build-qnx.yml, .github/RELEASE_TEMPLATE.md, and docs/release_notes/release_note_v_*.rst. Create the workflow and template so the listed acceptance criteria are met: dispatch by tag, verified Linux and QNX builds, attached coverage, and a draft release with available notes.

Written by the indexing model from the issue text.