updated the release tag for pipeline action and added the content permision for CLI update workflow

Author: shailesh-veracode

.github/workflows/binary-ready-veracode-sast-pipeline-scan.yml

@@ -72,7 +72,7 @@ jobs:
 
       - name: Veracode Pipeline-Scan
         id: pipeline-scan
-        uses: veracode/[email protected].14
+        uses: veracode/[email protected].15
         with:
           vid: ${{ secrets.VERACODE_API_ID }}
           vkey: ${{ secrets.VERACODE_API_KEY }}

.github/workflows/veracode-pipeline-scan.yml

@@ -73,7 +73,7 @@ jobs:
       # run the pipeline scan action
       - name: Veracode Pipeline-Scan
         id: pipeline-scan
-        uses: veracode/[email protected].14
+        uses: veracode/[email protected].15
         with:
           vid: ${{ secrets.VERACODE_API_ID }}
           vkey: ${{ secrets.VERACODE_API_KEY }}

veracode.yml

@@ -86,7 +86,7 @@ veracode_iac_secrets_scan:
   # If the break_build_on_error is set to true, the build will break if the scan failed to complete or with an error, no libraries were found, 
   # or no build system was found and the error_message will be displayed.
   break_build_on_error: true
-  error_message: "Veracode SCA scan faced a problem. Please contact your Veracode administrator for more information."
+  error_message: "Veracode IAC secrets scan faced a problem. Please contact your Veracode administrator for more information."
   # If the trigger is set to true, a scan is triggered when you create an issue containing the commands value or add a comment containing the commands value to an issue.
   # Syntax to be used - COMMANDS_VALUE [branch: BRANCH_NAME]
   issues: