feat: Add version check (command) (#421)

* chore: Adjust Rust toolchain in rustfmt override

* chore: Add built

* feat: Add release check (command)

* refactor: Update transfer client and cache related code

* chore: Apply suggestions

Co-authored-by: Nick <10092581+NickLarsenNZ@users.noreply.github.com>

* chore: Revert accidental commented-out instrument attribute

* chore: Add timeout to version check

---------

Co-authored-by: Nick <10092581+NickLarsenNZ@users.noreply.github.com>

Author: Techassi

.vscode/settings.json

@@ -3,7 +3,7 @@
   "rust-analyzer.cargo.features": "all",
   "rust-analyzer.rustfmt.overrideCommand": [
     "rustfmt",
-    "+nightly-2025-01-15",
+    "+nightly-2025-10-23",
     "--edition",
     "2024",
     "--"

Cargo.lock

@@ -22,6 +22,7 @@ axum = { version = "0.7", features = ["http2"] }
 axum-extra = { version = "0.9", features = ["typed-header"] }
 bcrypt = "0.15"
 bindgen = "0.70.1"
+built = "0.8.0"
 cc = "1.0.106"
 clap = { version = "4.5", features = ["derive", "env"] }
 clap_complete = "4.5"

Cargo.nix

@@ -14,5 +14,6 @@ Commands:
   completions         Generate shell completions for this tool
   cache               Interact with locally cached files
   experimental-debug  EXPERIMENTAL: Launch a debug container for a Pod
+  version             Retrieve version data of the stackablectl installation
   help                Print this message or the help of the given subcommand(s)
 ----

Cargo.toml

@@ -14,6 +14,7 @@ Commands:
   completions         Generate shell completions for this tool
   cache               Interact with locally cached files
   experimental-debug  EXPERIMENTAL: Launch a debug container for a Pod
+  version             Retrieve version data of the stackablectl installation
   help                Print this message or the help of the given subcommand(s)
 
 Options:

docs/modules/stackablectl/partials/commands/help.adoc

@@ -0,0 +1,95 @@
+// Autogenerated by cargo xtask gen-docs. DO NOT CHANGE MANUALLY!
+[source,console]
+----
+Retrieve version data of the stackablectl installation
+
+Usage: stackablectl version [OPTIONS] <COMMAND>
+
+Commands:
+  check  Check if there is a new version available
+  help   Print this message or the help of the given subcommand(s)
+
+Options:
+  -l, --log-level <LOG_LEVEL>
+          Log level this application uses
+
+      --no-cache
+          Do not cache the remote (default) demo, stack and release files
+
+          Cached files are saved at '$XDG_CACHE_HOME/stackablectl', which is usually
+          '$HOME/.cache/stackablectl' when not explicitly set.
+
+  -h, --help
+          Print help (see a summary with '-h')
+
+  -V, --version
+          Print version
+
+File options:
+  -d, --demo-file <DEMO_FILE>
+          Provide one or more additional (custom) demo file(s)
+
+          Demos are loaded in the following order: Remote (default) demo file, custom
+          demo files provided via the 'STACKABLE_DEMO_FILES' environment variable, and
+          lastly demo files provided via the '-d/--demo-file' argument(s). If there are
+          demos with the same name, the last demo definition will be used.
+
+          Use "stackablectl [OPTIONS] <COMMAND> -d path/to/demos1.yaml -d path/to/demos2.yaml"
+          to provide multiple additional demo files.
+
+  -s, --stack-file <STACK_FILE>
+          Provide one or more additional (custom) stack file(s)
+
+          Stacks are loaded in the following order: Remote (default) stack file, custom
+          stack files provided via the 'STACKABLE_STACK_FILES' environment variable, and
+          lastly demo files provided via the '-s/--stack-file' argument(s). If there are
+          stacks with the same name, the last stack definition will be used.
+
+          Use "stackablectl [OPTIONS] <COMMAND> -s path/to/stacks1.yaml -s path/to/stacks2.yaml"
+          to provide multiple additional stack files.
+
+  -r, --release-file <RELEASE_FILE>
+          Provide one or more additional (custom) release file(s)
+
+          Releases are loaded in the following order: Remote (default) release file,
+          custom release files provided via the 'STACKABLE_RELEASE_FILES' environment
+          variable, and lastly release files provided via the '-r/--release-file'
+          argument(s). If there are releases with the same name, the last release
+          definition will be used.
+
+          Use "stackablectl [OPTIONS] <COMMAND> -r path/to/releases1.yaml -r path/to/releases2.yaml"
+          to provide multiple additional release files.
+
+Helm repository options:
+      --helm-repo-stable <URL>
+          Provide a custom Helm stable repository URL
+
+          [default: https://repo.stackable.tech/repository/helm-stable/]
+
+      --helm-repo-test <URL>
+          Provide a custom Helm test repository URL
+
+          [default: https://repo.stackable.tech/repository/helm-test/]
+
+      --helm-repo-dev <URL>
+          Provide a custom Helm dev repository URL
+
+          [default: https://repo.stackable.tech/repository/helm-dev/]
+
+      --chart-source <CHART_SOURCE>
+          Source the charts from either a OCI registry or from index.yaml-based repositories.
+
+          Possible values:
+          - oci:  OCI registry
+          - repo: index.yaml-based repositories: resolution (dev, test, stable) is based on the version and thus will be operator-specific
+
+          [default: oci]
+
+Operator specific configurations:
+      --listener-class-preset <LISTENER_CLASS_PRESET>
+          Choose the ListenerClass preset (`none`, `ephemeral-nodes` or `stable-nodes`).
+
+          This maps to the listener-operator Helm Chart preset value, see [the listener-operator documentation](https://docs.stackable.tech/home/nightly/listener-operator/listenerclass/#presets) for details.
+
+          [possible values: none, stable-nodes, ephemeral-nodes]
+----