Fix PowerShell here-string parser error in vendor.yml

[Copilot]

PowerShell requires the "@ here-string terminator to be at column 0. Inside the if/else block in Summary - Update check results, the terminators were indented 10 spaces in YAML — but the run: | block only strips 8 spaces of base indentation, leaving 2 leading spaces in the generated script and triggering:

ParserError: White space is not allowed before the string terminator.

Changes

• vendor.yml — Replace two indented here-strings (inside if/else) with equivalent double-quoted strings using `n for newlines:

-          $summary = @"
-          ### ✅ No Updates Available
-
-          All vendor dependencies are up to date! 🎉
-          "@
+          $summary = "### ✅ No Updates Available`n`nAll vendor dependencies are up to date! 🎉`n"

[Copilot]

Pull request overview

This PR fixes a PowerShell parsing failure in the Summary - Update check results step by eliminating indented here-strings whose terminators were not at column 0 after YAML indentation was applied.

Changes:

• Replaced two PowerShell here-strings inside an if/else block with equivalent double-quoted strings using `n for newlines.
• Preserved the existing summary formatting behavior while preventing ParserError: White space is not allowed before the string terminator.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.