Fix shell script quote mismatch errors in docs-quality workflow

[Copilot]

This PR fixes shell script syntax errors in the documentation quality workflow that were causing the build to fail with `unexpected EOF while looking for matching '``.

Issues Fixed

The workflow contained multiple quote-related problems in shell script steps:

1. Improper variable interpolation with single quotes: Lines using echo '💻 Code examples: $code_blocks' were not expanding variables because single quotes prevent variable interpolation in bash.

2. Backtick matching issues: The grep pattern grep -r "```" docs/ was causing shell parsing errors due to backticks inside double quotes.

Changes Made

• Line 28: Changed echo '💻 Code examples: $code_blocks' to echo "💻 Code examples: $code_blocks" to enable proper variable interpolation
• Line 43: Changed echo '- 💻 Code examples: $code_blocks' to echo "- 💻 Code examples: $code_blocks" for consistent variable expansion
• Line 27: Changed grep -r "```" to grep -r '```' to avoid shell backtick interpretation issues

Example

Before (broken):

code_blocks=$(grep -r "```" docs/ | wc -l)  # Shell parsing error
echo '💻 Code examples: $code_blocks'        # Outputs literal: $code_blocks

After (fixed):

code_blocks=$(grep -r '```' docs/ | wc -l)   # Clean grep pattern
echo "💻 Code examples: $code_blocks"        # Outputs expanded: 💻 Code examples: 42

The workflow now properly counts documentation metrics and generates the GitHub step summary without syntax errors.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.