lf: build with cgo=0, run checks

[dkwo]

build static as suggested by upstream, run checks. cc maintainer @TeddyDD

• I tested the changes in this PR: yes
• I built this PR locally for my native architecture, (x86_64)
• I built this PR locally for these architectures (cross aarch64-musl)

[TeddyDD]

What's the added value of building this statically for system-wide installation? From what I see, Void defaults to CGO_ENABLED=1

[dkwo]

That's what upstream does and suggests. What's the disadvantage?

[TeddyDD]

That's what upstream does and suggests

It's not a strong suggestion, just copy-paste instruction for people who want to build it from source.
Half of programs written in Go suggest you should do static build so you can copy binary around.

For whatever reason, Void doesn't do this, and I fell like exceptions shoud be justified.

[dkwo]

Fair enough.