Release Signer Alongside Node

[BowTiedDevOps]

The aim of this PR is to create a signer release every time there is a core release happening, with the tag set as <core_release>.0.

This PR also moves most of the release workflow out of stacks-core and into actions repository such that on subsequent changes to the release process, we can easier adjust the workflows without the need of stacks-core pull requests.

I've also implemented latest docker image tags on non-RC releases and removed the signer- word from the signer version tag as it was redundant.

Example workflows (tests commented out for quicker workflow runs, but they are unaffected by these changes):

• Node Release (built both 4.0.0.0.0 and signer-4.0.0.0.0.0 releases): https://github.com/BowTiedDevOps/stacks-core/actions/runs/11963198211
• Standalone Signer Release (built signer-4.0.0.0.0.1 release): https://github.com/BowTiedDevOps/stacks-core/actions/runs/11963781406
• Standalone Signer RC Release (built signer-4.0.0.0.0.2-rc1 release, used to test that docker image latest doesn't update on RC builds): https://github.com/BowTiedDevOps/stacks-core/actions/runs/11963969804

Useful Links:

• Releases Page: https://github.com/BowTiedDevOps/stacks-core/releases
• Stacks Core Docker Images: https://hub.docker.com/r/bowtieddevops/stacks-core/tags
• Stacks Signer Docker Images: https://hub.docker.com/r/bowtieddevops/stacks-signer/tags

Binaries Version Check:

• Node Release

  $ ./stacks-node version
  INFO [1732236056.645827] [testnet/stacks-node/src/main.rs:283] [main] stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, 
  release build, linux [x86_64])
  stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])
  
  $ ./stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])

• Signer Release Built Alongside Node

  $ ./stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])

• Standalone Signer Release:

  $ ./stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.1 (release/signer-4.0.0.0.0.1:eb8aaf7, release build, linux [x86_64])

• Standalone Signer Release (RC Build):

  $ ./stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.2-rc1 (release/signer-4.0.0.0.0.2-rc1:eb8aaf7, release build, linux [x86_64])

Docker Images Version Check:

• Node

  $ docker run bowtieddevops/stacks-core:4.0.0.0.0 stacks-node version
  stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])
  INFO [1732236172.154954] [testnet/stacks-node/src/main.rs:283] [main] stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, 
  release build, linux [x86_64])
  
  $ docker run bowtieddevops/stacks-core:latest stacks-node version
  INFO [1732236216.647136] [testnet/stacks-node/src/main.rs:283] [main] stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, 
  release build, linux [x86_64])
  stacks-node 4.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])

• Signer

  $ docker run bowtieddevops/stacks-signer:4.0.0.0.0.0 stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.0 (release/4.0.0.0.0:eb8aaf7, release build, linux [x86_64])
  
  $ docker run bowtieddevops/stacks-signer:4.0.0.0.0.1 stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.1 (release/signer-4.0.0.0.0.1:eb8aaf7, release build, linux [x86_64])
  
  $ docker run bowtieddevops/stacks-signer:4.0.0.0.0.2-rc1 stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.2-rc1 (release/signer-4.0.0.0.0.2-rc1:eb8aaf7, release build, linux [x86_64])
  
  $ docker run bowtieddevops/stacks-signer:latest stacks-signer --version
  stacks-signer stacks-signer 4.0.0.0.0.1 (release/signer-4.0.0.0.0.1:eb8aaf7, release build, linux [x86_64])

[wileyj]

looks great! some minor changes (mostly cosmetic) but otherwise it looks ready to merge.

we'll want to cooridinate with the stacks-core PR on when to merge though, else it may break some workflows