feat(_release-rust): product-generic .deb path (binary_name + optional -p)

[emmanuelm41]

What

Makes the Debian .deb build step in the reusable workflow .github/workflows/_release-rust.yml product-generic, instead of hardcoding kache.

Two changes to the Build Debian package step:

1. Deb filename derives from inputs.binary_name — ${BINARY_NAME}_${VERSION}_${ARCH}.deb instead of the literal kache_…. BINARY_NAME: ${{ inputs.binary_name }} is added to the step env:.
2. New optional input deb_package (string, default ""). When set, -p "$DEB_PACKAGE" is passed to cargo deb via ${DEB_PACKAGE:+-p "$DEB_PACKAGE"}; when empty, the command runs exactly as today (no -p).

-          DEB="kache_${VERSION}_${ARCH}.deb"
-          cargo deb --no-build --target "$TARGET" --output "$DEB"
+          DEB="${BINARY_NAME}_${VERSION}_${ARCH}.deb"
+          cargo deb --no-build ${DEB_PACKAGE:+-p "$DEB_PACKAGE"} --target "$TARGET" --output "$DEB"

The signing / notarize / bare-exe / build steps are untouched.

Backward compatibility (kache)

100% backward-compatible for the existing consumer kunobi-ninja/kache:

• kache's binary_name is kache, so ${BINARY_NAME}_… → kache_<version>_<arch>.deb — identical asset name.
• kache does not set deb_package, so it defaults to "" → ${DEB_PACKAGE:+…} expands to nothing → cargo deb runs exactly as before (no -p, root package).

No behavior change for any current caller.

What it unblocks

Cargo-workspace consumers whose CLI lives in a member crate. e.g. kunobi-ninja/kobe: binary kobe, built from -p kobe-ctl, producing kobe_<version>_<arch>.deb. It only needs binary_name: kobe + deb_package: kobe-ctl.

Notes

• actionlint passes on the changed step (the few shellcheck infos it reports are pre-existing on unrelated steps, not introduced here).
• Versioning: a new tag (e.g. v12) should be cut after kache's release path is re-verified green against this branch, so workspace consumers can pin to it.