feat: add build flags for reduced binary size

[nmgaston]

Build Variants

• noui: Excludes web UI (~100MB reduction when UI assets embedded)

Binary Sizes (with UI assets embedded)

• Full (with UI): ~160MB unstripped, ~100MB stripped
• Headless (no UI): ~60MB unstripped, ~42MB stripped

Key Features

• Fully static binaries using CGO_ENABLED=0 with pure Go dependencies (modernc.org/sqlite, jackc/pgx/v5)
• Minimal Docker images using FROM scratch (no OS packages, ~0MB base)
• Conditional compilation: features automatically included/excluded based on build tags

Release Artifacts
Each platform (Linux, Windows, macOS) produces 3 binaries:

1. Full: SQLite + UI support
2. Headless: SQLite, no UI

CI/CD Updates

• All workflows build and test multiple variants with proper CGO settings

[nmgaston]

@rsdmike - Since there isn't a size advantage to the nosqlite flag, I question if we should include it. Found that we actually don't need CGO_ENABLED=1 in any of the build cases, which I think is what we were trying to do with that particular flag. It seems like it's adding unneeded complexity without any real advantage. Major advantage to the 'noui' flag. Thoughts?

[rsdmike]

@rsdmike - Since there isn't a size advantage to the nosqlite flag, I question if we should include it. Found that we actually don't need CGO_ENABLED=1 in any of the build cases, which I think is what we were trying to do with that particular flag. It seems like it's adding unneeded complexity without any real advantage. Major advantage to the 'noui' flag. Thoughts?

I agree, if it doesnt add value, lets not complicate the build. I say lets get rid of it. For history, I think the CGO requirement originally came from https://github.com/99designs/keyring which used the C Bindings for the keyring. Recently we switched to https://github.com/zalando/go-keyring which is pure go. Similar story for sqlite (used originally the CGO version then the pure go version). So now that we are pure go, we can greatly simplify the CI/CD workflow as we no longer need to coordinate the build across multiple OSes. However, we'll save that optimization I think for a different PR and just remove the nosqlite in this one.

FWIW, I did see about a 3MB reduction with removing SQLite, but still not materially different to warrant the extra build complexity.

Thank you for doing this!

[RosieAMT]

🎉 This PR is included in version 1.18.0 🎉

The release is available on:

• GitHub release
• v1.18.0

Your semantic-release bot 📦🚀