Release: Run cli tests daily (#449)

* Add cron job to main.yml to run tests every weekday morning

* Update cron job to only run on weekdays

Author: sami-alajrami

docs.kosli.com/assets/metadata.json

@@ -1 +1 @@
-{"currentversion": "v2.11.8"}
+{"currentversion": "v2.11.9"}

docs.kosli.com/content/client_reference/kosli_assert_artifact.md

@@ -58,7 +58,7 @@ In [this YAML file](https://app.kosli.com/api/v2/livedocs/cyber-dojo/yaml?ci=git
 kosli assert artifact \
 	--fingerprint 184c799cd551dd1d8d5c5f9a5d593b2e931f5e36122ee5c793c1d08a19839cc0 \
 	--flow yourFlowName \
-	--against-env prod \
+	--environment prod \
 	--api-token yourAPIToken \
 	--org yourOrgName 
 

docs.kosli.com/content/client_reference/kosli_attest_sonar.md

@@ -2,26 +2,26 @@
 title: "kosli attest sonar"
 beta: false
 deprecated: false
-summary: "Report a SonarCloud or SonarQube attestation to an artifact or a trail in a Kosli flow.  "
+summary: "Report a SonarQube attestation to an artifact or a trail in a Kosli flow.  "
 ---
 
 # kosli attest sonar
 
 ## Synopsis
 
-Report a SonarCloud or SonarQube attestation to an artifact or a trail in a Kosli flow.  
-Retrieves results for the specified scan from SonarCloud or SonarQube and attests them to Kosli.
+Report a SonarQube attestation to an artifact or a trail in a Kosli flow.  
+Retrieves results for the specified scan from SonarQube Cloud or SonarQube Server and attests them to Kosli.
 The results are parsed to find the status of the project's quality gate which is used to determine the attestation's compliance status.
 
 The scan to be retrieved can be specified in two ways:
 1. (Default) Using metadata created by the Sonar scanner. By default this is located within a temporary .scannerwork folder in the repo base directory.
 If you have overriden the location of this folder by passing parameters to the Sonar scanner, or are running Kosli's CLI locally outside the repo's base directory,
 you can provide the correct path using the --sonar-working-dir flag. This metadata is generated by a specific scan, allowing Kosli to retrieve the results of that scan.
 2. Providing the Sonar project key and the revision of the scan (plus the SonarQube server URL if relevant). If running the Kosli CLI in some CI/CD pipeline, the revision
-is defaulted to the commit SHA. If you are running the command locally, or have overriden the revision in SonarCloud/SonarQube via parameters to the Sonar scanner, you can
+is defaulted to the commit SHA. If you are running the command locally, or have overriden the revision in SonarQube via parameters to the Sonar scanner, you can
 provide the correct revision using the --sonar-revision flag. Kosli then finds the scan results for the specified project key and revision.
 
-Note that if your project is very large and you are using SonarCloud's automatic analysis, it is possible for the attest sonar command to run before the SonarCloud scan is completed.
+Note that if your project is very large and you are using SonarQube Cloud's automatic analysis, it is possible for the attest sonar command to run before the SonarQube Cloud scan is completed.
 In this case, we recommend using Kosli's Sonar webhook integration ( https://docs.kosli.com/integrations/sonar/ ) rather than the CLI to attest the scan results.
 
 
@@ -85,7 +85,7 @@ In [this YAML file](https://app.kosli.com/api/v2/livedocs/cyber-dojo/yaml?ci=git
 
 ## Examples Use Cases
 
-**report a sonarcloud attestation about a trail using Sonar's metadata**
+**report a SonarQube Cloud attestation about a trail using Sonar's metadata**
 
 ```shell
 kosli attest sonar \
@@ -99,7 +99,7 @@ kosli attest sonar \
 
 ```
 
-**report a sonarqube attestation about a trail using Sonar's metadata**
+**report a SonarQube Server attestation about a trail using Sonar's metadata**
 
 ```shell
 kosli attest sonar \
@@ -113,7 +113,7 @@ kosli attest sonar \
 
 ```
 
-**report a sonarcloud attestation for a specific branch about a trail using key/revision**
+**report a SonarQube Cloud attestation for a specific branch about a trail using key/revision**
 
 ```shell
 kosli attest sonar \
@@ -129,7 +129,7 @@ kosli attest sonar \
 
 ```
 
-**report a sonarqube attestation for a pull-request about a trail using key/revision**
+**report a SonarQube Server attestation for a pull-request about a trail using key/revision**
 
 ```shell
 kosli attest sonar \
@@ -146,7 +146,7 @@ kosli attest sonar \
 
 ```
 
-**report a sonarcloud attestation about a trail with an attachment using Sonar's metadata**
+**report a SonarQube Cloud attestation about a trail with an attachment using Sonar's metadata**
 
 ```shell
 kosli attest sonar \

docs.kosli.com/content/legacy_ref/v2.11.3/_index.md

@@ -1,7 +1,7 @@
 ---
 title: v2.11.4
 bookCollapseSection: true
-weight: 603
+weight: 604
 ---
 
 # v2.11.4

docs.kosli.com/content/legacy_ref/v2.11.4/_index.md

@@ -1,7 +1,7 @@
 ---
 title: v2.11.5
 bookCollapseSection: true
-weight: 602
+weight: 603
 ---
 
 # v2.11.5

docs.kosli.com/content/legacy_ref/v2.11.5/_index.md

@@ -1,7 +1,7 @@
 ---
 title: v2.11.6
 bookCollapseSection: true
-weight: 601
+weight: 602
 ---
 
 # v2.11.6

docs.kosli.com/content/legacy_ref/v2.11.6/_index.md

@@ -1,7 +1,7 @@
 ---
 title: v2.11.7
 bookCollapseSection: true
-weight: 600
+weight: 601
 ---
 
 # v2.11.7

docs.kosli.com/content/legacy_ref/v2.11.7/_index.md

@@ -0,0 +1,7 @@
+---
+title: v2.11.8
+bookCollapseSection: true
+weight: 600
+---
+
+# v2.11.8

docs.kosli.com/content/legacy_ref/v2.11.8/_index.md

@@ -2,6 +2,7 @@
 title: "kosli"
 beta: false
 deprecated: false
+summary: "The Kosli CLI."
 ---
 
 # kosli