👷 Release server binary

[JMicheli]

This pull request adds a new workflow to build and release a binary package of the Stump server, so that users can directly run the server rather than using a Docker container. It aims to close #310 once complete.

The workflow is intended to be manually triggered, with the desired version number/tag for the release being input at that time. For example, the user could trigger the workflow with version = 1.0.0 and the result would be a draft release called "Release 1.0.0" tagged "v1.0.0."

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

[JMicheli]

I just pushed another commit that cleans up the testing stuff since this appears to be working. Won't be shocked if it requires further tuning, but I think it's likely ready to merge in.

One thought: should it be merged with main instead since it probably needs to be for the action to be manually triggered, and that's where releases come from anyhow?

[aaronleopold]

One thought: should it be merged with main instead since it probably needs to be for the action to be manually triggered, and that's where releases come from anyhow?

It's okay to merge into develop, it'll be in main before the next release (I create the tag after merge to main, which triggers the docker build)

[aaronleopold]

LGTM! Thanks for knocking this out!