Stop GPG-signing binaries, since it consumes human time when releasing

Author: valeriansaliou

PACKAGING.md

@@ -13,5 +13,4 @@ We consider here the packaging flow of Raider version `1.0.0` for Linux.
 2. **How to build Raider, package it and release it on Crates, GitHub, Docker Hub and Packagecloud (multiple architectures):**
     1. Tag the latest Git commit corresponding to the release with tag `v1.0.0`, and push the tag
     2. Wait for all release jobs to complete on the [actions](https://github.com/valeriansaliou/raider/actions) page on GitHub
-    3. Download all release archives, and sign them locally using: `./scripts/sign_binaries.sh --version=1.0.0`
-    4. Publish a changelog and upload all the built archives, as well as their signatures on the [releases](https://github.com/valeriansaliou/raider/releases) page on GitHub
+    3. Publish a changelog and upload all the built archives on the [releases](https://github.com/valeriansaliou/raider/releases) page on GitHub

README.md

@@ -53,8 +53,6 @@ The best way to install Raider is to pull the latest release from the [Raider re
 
 Make sure to pick the correct server architecture (eg. Intel 32 bits).
 
-👉 _Each release binary comes with an `.asc` signature file, which can be verified using [@valeriansaliou](https://github.com/valeriansaliou) GPG public key: [:key:valeriansaliou.gpg.pub.asc](https://valeriansaliou.name/files/keys/valeriansaliou.gpg.pub.asc)._
-
 **Install from packages:**
 
 Raider provides [pre-built packages](https://packagecloud.io/valeriansaliou/raider) for Debian-based systems (Debian, Ubuntu, etc.).