Bug: Rover log flag log-severity command not found

Running Rover in Azure DevOps with a Linux VM, adding the flag -log-severity to set the terraform log level to any value gives the error:
`
-log-severity: command not found
##[error]Bash exited with code '127'.
`
## Rover Version
`
aztfmod/rover:1.6.6.-2401.0402
`

The following is the script we are executing from our pipeline:
```
- script: |
export ROVER_RUNNER=true
/tf/rover/rover.sh \
-lz $(Build.SourcesDirectory)/Library/$(landingzone_version) \
-var-folder $(Build.SourcesDirectory)/${{ parameters.repoName }}/variables \
-a apply \
-level $(level) \
-env test \
-log-severity $(tflog_level)
-tfstate_subscription_id $(ARM_SUBSCRIPTION_ID) \
-tfstate $(tfstate_name).tfstate \
-target_subscription $(target_subscription) \
-p plan.tfstate.tfplan/drop/plan.tfstate.tfplan
```

We tried setting the -log-severity to DEBUG or TRACE directly the pipeline failed with the same error.
https://aztfmod.github.io/documentation/docs/rover/rover-commands/
https://developer.hashicorp.com/terraform/internals/debugging

---
**Review Note (2026-01-12)**: This is a critical bug affecting CI/CD pipelines. The -log-severity flag is not working as documented, preventing users from debugging Terraform issues.

Start by running the supplied Azure DevOps Bash snippet and inspect rover.sh handling of -log-severity, then compare it with the documented rover command and Terraform debugging guidance. Verify whether the flag reaches Terraform as one argument and confirm completion when DEBUG or TRACE produces the expected Terraform log level without a shell error.

Written by the indexing model from the issue text.