fix: Replace github-script with gh CLI for PR comments

Replace the complex github-script action with a simple gh CLI command
to avoid YAML parsing issues with JavaScript template literals.

Issue:
  Invalid workflow file: .github/workflows/chart-lock-check.yaml#L64
  You have an error in your yaml syntax on line 64

Root Cause:
GitHub's YAML parser was having issues with the JavaScript template
literal string concatenation inside the github-script action, even
though it was technically valid.

Solution:
Use the GitHub CLI (gh) which is pre-installed on GitHub runners:
  gh pr comment ${{ github.event.pull_request.number }} --body "..."

Benefits:
✅ No JavaScript/YAML escaping conflicts
✅ Simpler and more readable
✅ Native multi-line string support
✅ No external action dependency (uses built-in gh CLI)
✅ Same functionality, cleaner implementation

Author: fidencio

.github/workflows/chart-lock-check.yaml

@@ -48,39 +48,42 @@ jobs:
 
       - name: Add comment to PR
         if: steps.check.outputs.has_dev_version == 'true'
-        uses: actions/github-script@v7
-        with:
-          script: |
-            await github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: '## ❌ Chart.lock Contains 0.0.0-dev Entries\n\n' +
-                    'Found `0.0.0-dev` entries in `Chart.lock` that must be removed.\n\n' +
-                    '**Why this is a problem:**\n' +
-                    'The `kata-as-coco-runtime-for-ci` dependency uses `version: 0.0.0-dev` which is:\n' +
-                    '- Only for CI testing\n' +
-                    '- Not a real release\n' +
-                    '- Should never be committed to Chart.lock\n\n' +
-                    '**How to fix:**\n\n' +
-                    'Manually edit Chart.lock to remove the entire dependency block containing `version: 0.0.0-dev`:\n\n' +
-                    '```yaml\n' +
-                    '# Remove this entire block from Chart.lock:\n' +
-                    '- name: kata-deploy\n' +
-                    '  repository: oci://ghcr.io/kata-containers/kata-deploy-charts\n' +
-                    '  version: 0.0.0-dev\n' +
-                    '```\n\n' +
-                    'Then commit and push:\n' +
-                    '```bash\n' +
-                    'git add Chart.lock\n' +
-                    'git commit -m "fix: Remove 0.0.0-dev from Chart.lock"\n' +
-                    'git push\n' +
-                    '```\n\n' +
-                    '**Why not regenerate with helm dependency update?**\n' +
-                    'Running `helm dependency update` would add the 0.0.0-dev entry back. This entry only exists for CI testing and should never be in Chart.lock.\n\n' +
-                    '**Prevention:**\n' +
-                    'Chart.lock is managed by CI/CD workflows. Don\'t manually run `helm dependency update` - the prepare-release script handles updates correctly.'
-            });
+        run: |
+          gh pr comment ${{ github.event.pull_request.number }} --body "## ❌ Chart.lock Contains 0.0.0-dev Entries
+
+          Found \`0.0.0-dev\` entries in \`Chart.lock\` that must be removed.
+
+          **Why this is a problem:**
+          The \`kata-as-coco-runtime-for-ci\` dependency uses \`version: 0.0.0-dev\` which is:
+          - Only for CI testing
+          - Not a real release
+          - Should never be committed to Chart.lock
+
+          **How to fix:**
+
+          Manually edit Chart.lock to remove the entire dependency block containing \`version: 0.0.0-dev\`:
+
+          \`\`\`yaml
+          # Remove this entire block from Chart.lock:
+          - name: kata-deploy
+            repository: oci://ghcr.io/kata-containers/kata-deploy-charts
+            version: 0.0.0-dev
+          \`\`\`
+
+          Then commit and push:
+          \`\`\`bash
+          git add Chart.lock
+          git commit -m \"fix: Remove 0.0.0-dev from Chart.lock\"
+          git push
+          \`\`\`
+
+          **Why not regenerate with helm dependency update?**
+          Running \`helm dependency update\` would add the 0.0.0-dev entry back. This entry only exists for CI testing and should never be in Chart.lock.
+
+          **Prevention:**
+          Chart.lock is managed by CI/CD workflows. Don't manually run \`helm dependency update\` - the prepare-release script handles updates correctly."
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Fail if 0.0.0-dev found
         if: steps.check.outputs.has_dev_version == 'true'