CLI: rename the binary svix-cli -> svix (#1605)

We flip-flopped on this. For now, let's call the binary `svix`.

`dist plan` shows that the various build artifacts will still be named
`svix-cli` which is what we want.

```
$ dist plan
announcing v1.45.0
  svix-cli 1.45.0
    source.tar.gz
      [checksum] source.tar.gz.sha256
    svix-cli-installer.sh
    svix-cli-installer.ps1
    sha256.sum
    svix-cli-aarch64-apple-darwin-update
    svix-cli-aarch64-apple-darwin.tar.xz
      [bin] svix
      [misc] LICENSE, README.md
      [checksum] svix-cli-aarch64-apple-darwin.tar.xz.sha256
    svix-cli-aarch64-unknown-linux-gnu-update
    svix-cli-aarch64-unknown-linux-gnu.tar.xz
      [bin] svix
      [misc] LICENSE, README.md
      [checksum] svix-cli-aarch64-unknown-linux-gnu.tar.xz.sha256
    svix-cli-x86_64-apple-darwin-update
    svix-cli-x86_64-apple-darwin.tar.xz
      [bin] svix
      [misc] LICENSE, README.md
      [checksum] svix-cli-x86_64-apple-darwin.tar.xz.sha256
    svix-cli-x86_64-pc-windows-msvc-update
    svix-cli-x86_64-pc-windows-msvc.zip
      [bin] svix.exe
      [misc] LICENSE, README.md
      [checksum] svix-cli-x86_64-pc-windows-msvc.zip.sha256
    svix-cli-x86_64-pc-windows-msvc.msi
      [bin] svix.exe
      [checksum] svix-cli-x86_64-pc-windows-msvc.msi.sha256
    svix-cli-x86_64-unknown-linux-musl-update
    svix-cli-x86_64-unknown-linux-musl.tar.xz
      [bin] svix
      [misc] LICENSE, README.md
      [checksum] svix-cli-x86_64-unknown-linux-musl.tar.xz.sha256
```

The one wart with this change is how folks installing via the script
installers will end up with the main binary named `svix` and an updater
called `svix-cli-updater`, but in this case I think that's okay.

svix-cli/Cargo.toml

@@ -20,6 +20,10 @@ path-guid = "2E3464D5-DAC5-4C00-A074-250BB17BBBE2"
 license = false
 eula = false
 
+[[bin]]
+name = "svix"
+path = "src/main.rs"
+
 [dependencies]
 anyhow = "1.0.94"
 base64 = "0.22.1"

svix-cli/README.md

@@ -37,14 +37,14 @@ These scripts will install the binaries to `~/.svix/bin` and also add this direc
 
 #### Manually
 
-Additionally, you can select executables to download directly from [our releases page](https://github.com/svix/svix-cli/releases), and use them as is without
+Additionally, you can select executables to download directly from [our releases page](https://github.com/svix/svix-webhooks/releases), and use them as is without
 having to install anything.
 
 1. Download and extract the archive for your operating system.
-2. Run the `svix-cli` executable from the command line: `./svix-cli help`.
+2. Run the `svix` executable from the command line: `./svix help`.
 
 > [!NOTE]
-> You may need to allow execution by running `chmod +x svix-cli`.
+> You may need to allow execution by running `chmod +x svix`.
 
 
 You can also put the binaries anywhere in your `PATH` so you can run the command from anywhere without needing to provide its full path. On macOS or Linux you can achieve this by moving the executable to `/usr/local/bin` or `/usr/bin`.
@@ -55,13 +55,13 @@ You can also put the binaries anywhere in your `PATH` so you can run the command
 Installing the Svix CLI provides access to the `svix` command.
 
 ```sh
-svix-cli [command]
+svix [command]
 
-# Run `svix-cli help` for information about the available commands
-svix-cli help
+# Run `svix help` for information about the available commands
+svix help
 
 # or add the `--help` flag to any command for a more detailed description and list of flags
-svix-cli [command] --help
+svix [command] --help
 ```
 
 
@@ -79,7 +79,7 @@ change any NAT configuration on your network.
 Example:
 
 ```sh
-svix-cli listen http://localhost:8000/webhook/
+svix listen http://localhost:8000/webhook/
 ```
 
 Output:
@@ -104,13 +104,13 @@ to `http://localhost:8000/webhook/`.
 # Set your Auth Token temporarily via the SVIX_AUTH_TOKEN environment variable
 export SVIX_AUTH_TOKEN=<MY-AUTH-TOKEN>
 # or to persistently store your auth token in a config file run
-svix-cli login # interactively configure your Svix API credentials
+svix login # interactively configure your Svix API credentials
 
 # Create an Application with the name "Demo"
-svix-cli application create '{ "name": "demo" }'
+svix application create '{ "name": "demo" }'
 
 # List Applications
-svix-cli application list --limit 2 --iterator some_iterator
+svix application list --limit 2 --iterator some_iterator
 ```
 
 ## Commands
@@ -138,16 +138,16 @@ The Svix CLI supports the following commands:
 
 Shell completion scripts are provided for `bash`, `elvish`, `fish`, `powershell`, and `zsh`.
 
-To generate a script for your shell type `svix-cli completion <SHELL NAME>`.
+To generate a script for your shell type `svix completion <SHELL NAME>`.
 
-For detailed instructions on configuring completions for your shell run `svix-cli completion --help`.
+For detailed instructions on configuring completions for your shell run `svix completion --help`.
 
 > [!TIP]
 > You can source the completion script automatically in your shell rc file.
 >
 > Example:
 > ```sh
-> eval "$(svix-cli completion bash)"
+> eval "$(svix completion bash)"
 > ```
 
 

svix-cli/wix/main.wxs

@@ -123,9 +123,9 @@
                         <Component Id='binary0' Guid='*'>
                             <File
                                 Id='exe0'
-                                Name='svix-cli.exe'
+                                Name='svix.exe'
                                 DiskId='1'
-                                Source='$(var.CargoTargetBinDir)\svix-cli.exe'
+                                Source='$(var.CargoTargetBinDir)\svix.exe'
                                 KeyPath='yes'/>
                         </Component>
                     </Directory>