Fix GitHub Actions step summary generation issues

[Copilot]

• Analyze the current issues with GITHUB_STEP_SUMMARY generation
• Fix the PowerShell echo command issues in build.yml (backticks and variable expansion)
• Add Cmder version to build workflow summary
• Fix the PowerShell echo command issues in tests.yml
• Enhance tests.yml to provide more verbose and useful information
• Fix the PowerShell echo command issues in codeql.yml
• Fix the PowerShell echo command issues in vendor.yml (critical Unicode escape error)
• Test the generated summaries locally with PowerShell to ensure correctness
• Add clickable links to repository, branch, commit, and actor in build summary
• Add ISO timestamp for build start time (with code formatting)
• Add vendor packages table from sources.json with link to sources.json and release links
• Show full SHA256 hashes (not truncated)
• Merge artifacts and upload sections into single table with download links
• Add section separators with --- (removed separator before artifacts)
• Reduce duplicate emoji usage
• Fix incomplete summary by initializing $summary variable before appending to it
• Combine backticks with links for code formatting on clickable values
• Simplify build success message to "Cmder built successfully"
• Reorder artifacts table columns (Download before Hash) for better readability
• Add file type emojis: 📄 for txt files, 🗄️ for archives, 📥 for download links
• Fetch real artifact download URLs using GitHub API with retry logic (3 attempts, 2s delay, ⚠️ warning on failure)
• Fix branch links for PR merge refs (e.g., 3061/merge) to point to PR page instead of invalid tree URL
• Verify all changes work correctly

Key Features

Direct Artifact Downloads

Implemented intelligent artifact URL fetching using GitHub CLI API:

• Automatically retrieves direct download links for all build artifacts
• Retry mechanism with 3 attempts and 2-second delays between retries
• Graceful fallback to workflow run page with ⚠️ warning indicator if API fails
• Uses GitHub token authentication for API access

Enhanced Summaries Across All Workflows

• build.yml: Comprehensive build information with Cmder version, vendor packages with release links, and artifact details with direct downloads
• tests.yml: Detailed test environment and results with individual test status
• codeql.yml: Security analysis workflow summary
• vendor.yml: Vendor update workflow with proper Unicode handling

All workflows now use PowerShell here-strings (@"..."@) instead of echo commands to eliminate Unicode escape sequence errors and ensure proper variable expansion.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[DRSDavidSoft]

@copilot critical issue, please resolve this one, it is related to the vendor update workflow task, which we haven't addressed yet:

ParserError: D:\a_temp\e73f58ac-3cd5-4466-98b3-07bb127fa841.ps1:6
Line |
6 | echo "Branch: `update-vendor`" >> $env:GITHUB_STEP_SUMMARY
| ~~
| The Unicode escape sequence is not valid. A valid sequence is `u{ followed by one to six hex digits and a
| closing '}'.
Error: Process completed with exit code 1.

[Copilot]

@copilot critical issue, please resolve this one, it is related to the vendor update workflow task, which we haven't addressed yet:

ParserError: D:\a_temp\e73f58ac-3cd5-4466-98b3-07bb127fa841.ps1:...

Fixed in commit 684185c. The issue was caused by using echo commands with backticks in the vendor workflow, which PowerShell interprets as Unicode escape sequences (\`).

Converted all echo commands to PowerShell here-strings (@"..."@) in vendor.yml, matching the pattern used in build.yml, tests.yml, and codeql.yml. This eliminates the escape character parsing errors while properly displaying backticks in the workflow summary output.

The workflow summary now correctly shows:

• Branch: `update-vendor`
• All other markdown formatting without Unicode escape errors

[daxgames]

@DRSDavidSoft I wish I could help you with this. I have no idea how most of this stuff works

[daxgames]

@DRSDavidSoft Sorry but I had to get these working. I tried to just fix them without losing any of your changes.

I think they are all at least working at this time.

Not sure they are exactly what you were trying to do yet .