Add --release flag to emulate real released binaries, rename release to nodebug

[jakebailey]

I want to be able to produce "real" release binaries, with stripping and trimming.

Shift stuff around to make that possible. Since --release is sort of overlapping with the build tag release, I renamed that to nodebug, matching noembed.

[Copilot]

Pull request overview

This PR introduces a --release flag to enable building production-ready binaries with debug information stripped and code trimmed. To avoid naming conflicts, the existing build tag release is renamed to nodebug to better align with the existing noembed tag naming convention.

Changes:

• Renamed the release build tag to nodebug in Go build constraint comments
• Added a --release command-line flag option
• Extracted release build flag generation into a reusable getReleaseBuildFlags() function
• Updated build processes to use the new release flag and function

Reviewed changes

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

File	Description
internal/debug/release.go	Updated build constraint from release to nodebug
internal/debug/debug.go	Updated negated build constraint to use !nodebug
Herebyfile.mjs	Added --release flag, extracted getReleaseBuildFlags() function, and updated build processes

[rubiesonthesky]

nodebug seems logical flag, but without context, it’s easy to read it as “node bug” 🐛 probably no harm, just funny coincidence.

[jakebailey]

Yes, I thought that was funny.

Can't think of a better name, though. I could probably just leave it as release but we haven't had any reasons to flip code around in release mode (usually a bad idea, I am questioning us doing it still).

[jakebailey]

Thinking more, we should have a --nodebug like --noembed, except that aliases another flag too. So, it's probably a bad build tag name and release was fine. Maybe...