docs: autoscaler config for blocking query timeout (#19777)

website/content/tools/autoscaling/agent/nomad.mdx

@@ -51,3 +51,6 @@ nomad {
 
 - `skip_verify` `(bool: false)` - Do not verify TLS certificates. This is strongly
   discouraged.
+
+- `block_query_wait_time` `(string: "5m")` - How long applicable Nomad API
+  requests supporting blocking queries are held open. Defaults to `5m`.

website/content/tools/autoscaling/cli.mdx

@@ -74,6 +74,9 @@ passed in via CLI arguments. The `agent` command accepts the following arguments
 
 - `-nomad-skip-verify`: Do not verify TLS certificates. This is strongly discouraged.
 
+- `-nomad-block-query-wait-time=<dur>`: How long applicable Nomad API requests
+  supporting blocking queries are held open. Defaults to `5m`.
+
 - `-policy-dir=<path>`: The path to a directory used to load scaling policies.
 
 - `-policy-default-cooldown=<dur>`: The default cooldown that will be applied to
@@ -172,6 +175,12 @@ passed in via CLI arguments. The `agent` command accepts the following arguments
   hold a lock over a Nomad variable and will only execute if the lock is
   successfully acquired. It defaults to `false`.
 
+- `-high-availability-lock-namepsace`: Defines the path of the Nomad namespace
+  where the variable that will be used to sync the leader when running in high
+  availability mode. This parameter needs to be the same on all Nomad
+  Autoscaler agents expected to take part in the same leadership election
+  process. Defaults to `default`.
+
 - `-high-availability-lock-path`: Defines the path of the Nomad variable that
   will be used to sync the leader when running in high availability mode. This
   parameter needs to be the same on all Nomad Autoscaler agents expected to