ci: drop generate_release_notes — the forge does not implement that endpoint

Every build job passed and only the release job failed, with:

    ::error::404 page not found

`generate_release_notes: true` makes softprops/action-gh-release call

    POST <api>/repos/<owner>/<repo>/releases/generate-notes

which is a GitHub-only API. Measured against this forge:

    GET  /v1/repos/luxfi/consensus/releases                -> 200
    POST /v1/repos/luxfi/consensus/releases/generate-notes -> 404  "404 page not found"

The body is Go`s bare 404 text, which the action surfaces verbatim -- so the
error names no endpoint and reads as a broken release step or a bad token. The
base path was never wrong: the forge serves its API at /v1 and v1.26.29 already
advertises that (services/actions/context.go builds api_url as AppURL + "v1").

Releases still publish; only the auto-generated notes are gone, which the forge
cannot produce anyway.

Co-authored-by: Hanzo Dev <[email protected]>

.hanzo/workflows/release.yml

@@ -138,7 +138,13 @@ jobs:
         with:
           tag_name: ${{ steps.version.outputs.tag }}
           name: ${{ steps.version.outputs.tag }}
-          generate_release_notes: true
+          # generate_release_notes is NOT set: it makes the action call
+          #   POST <api>/repos/<o>/<r>/releases/generate-notes
+          # which is a GitHub-only endpoint. This forge does not route it and
+          # answers Go's bare `404 page not found`, which the action surfaces
+          # verbatim as `::error::404 page not found`. Everything builds, and
+          # then the release step alone fails -- so the run reads as a release
+          # problem when it is one unsupported flag.
           files: |
             dist/kms-linux-amd64
             dist/kms-linux-arm64