feat: add OpenAPI schema build to release workflow

[CasLubbers]

No description provided.

[Copilot]

Pull request overview

Adds OpenAPI schema generation to the release workflow so the schema JSON can be published alongside each GitHub Release.

Changes:

• Set up Node.js in the release-software job.
• Run the OpenAPI/model build (npm ci + npm run build:models) during release.
• Upload the generated schema JSON as a release asset (skipped on dry_run).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Suppressed comments (1)

.github/workflows/release-software.yml:115

• This adds schema build/upload after the GitHub Release is created. If the schema build fails, the workflow will leave behind a published release (and potentially pushed image) without the OpenAPI asset. Also, gh release upload will fail on workflow reruns if the asset already exists. Consider (1) building the schema before creating the release, (2) using .nvmrc for the Node version to avoid duplicating version bumps, (3) using GH_TOKEN for gh (matching other workflows here), and (4) adding --clobber to make reruns idempotent.

      - name: Set up Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 24