feat(release): update goreleaser config to v2 and support darwin binaries

[rektdeckard]

• Updates goreleaser action to v7 and config to v2
• Adds support for darwin binaries in release workflow
• Removes support for windows-arm32 binaries in release workflow
• Bumps server-sdk-go

[real-danm]

See the release notes for bumping the sdk, you'll need to bump livekit-cli version as well:
https://github.com/livekit/livekit-cli?tab=readme-ov-file#release

[rektdeckard]

@real-danm i bumped server-sdk-go to v2.14.0 here because shawn already bumped CLI to v2.14.0 here. I had meant for him to increment the patch version :)

[davidzhao]

Adds support for darwin binaries in release workflow

Darwin binaries aren't executable without signing.. they should be getting the signed copies from homebrew instead.

[rektdeckard]

@davidzhao Is that true? Plenty of people are distributing binaries through homebrew, and the Gatekeeper quarantine procedure flags apps that are downloaded from quarantine-aware sources (browser, email, etc.) not as a blanket. Yes, you won't be able to download this directly from the browser and run it without the quarantine popup, but when fetched from homebrew and installed to /opt/homebrew it isn't subject to the same restrictions. Homebrew strips the quarantine attribute, if it is present.

And as I understand it, code signing is a different problem and is only enforced for .app bundles when launched via Finder or LaunchServices.

Part of the reason for this change is that @theomonnom is adding a lot of functionality to the CLI (console mode, simulations) that require a ton of vendored C libraries and bindings to Go, and it isn't going to be easy to make that work reliably if homebrew builds from source on the host machine as it currently does.