feat: Automate SIPNET binary builds and manual release

[AritraDey-Dev]

This pull request fixes #27

CI Workflow Enhancements:

• .github/workflows/ci.yml: Added a step to upload SIPNET binaries after the build step.
• .github/workflows/ci.yml: Introduced a new job to create a release, which includes checking out the code, creating a release, and uploading the release asset.

Makefile Updates:

• Makefile: Added a release target to the all target dependencies.
• Makefile: Defined the release target to package and compress the SIPNET binary and clean up the release directory.

[Alomir]

@AritraDey-Dev Thank you for the PR!

Do I read this correctly, that it will create a release and upload binaries on every PR push? That would be way to often; at most, it should be on merging with the master branch.

[dlebauer]

Awesome, thanks for taking this on @AritraDey-Dev

Two requests (with what I think the code would look like):

1. trigger on tags matching vX.Y.Z

on:
  push:
    tags:
      - 'v*.*.*'

2. create release as a draft

steps:
  ...
  with:
    ...
    draft: true

[AritraDey-Dev]

@dlebauer Thanks for the reviewing the PR.I will make those changes.

[AritraDey-Dev]

@AritraDey-Dev Thank you for the PR!

Do I read this correctly, that it will create a release and upload binaries on every PR push? That would be way to often; at most, it should be on merging with the master branch.

Yes, you're correct. The current setup would trigger a release on every PR push. We should modify it to only create a release and upload binaries upon merging into the master branch. Thank you for pointing that out!