Fix some ps1 issues

[quickquickcode]

Summary

This PR fixes a set of PowerShell string interpolation issues in wps-office-mcp/scripts/wps-com.ps1 that affect Excel range expressions involving row and column references.

The main change is replacing patterns like:

• "$col:$col"
• "$startRow:$endRow"

with explicit variable boundaries such as:

• "${col}:${col}"
• "${startRow}:${endRow}"

This avoids ambiguous parsing when a variable is immediately followed by : in a double-quoted string.

Why

In PowerShell, variable interpolation can become error-prone when variable names are directly adjacent to characters like :. Using ${...} makes the intended variable boundaries explicit and ensures the generated range string is correct.

This is especially important for COM calls like:

• Range(...).ColumnWidth = ...
• Range(...).AutoFit()
• Range(...).Insert()
• Range(...).Delete()
• Range(...).Hidden = $true / $false
• Range(...).Group()

Scope of changes

Updated Excel-related range construction in the following operations inside wps-com.ps1:

• set column width
• autofit column
• insert rows
• insert columns
• delete rows
• delete columns
• hide rows
• hide columns
• show rows
• show columns
• group columns

Impact

This change should improve reliability for Excel row/column range operations in the WPS COM bridge and prevent malformed range strings caused by ambiguous interpolation.

Notes

• The change is limited to string construction for range references.
• No intended behavior change beyond producing the correct COM range address.
• This PR is based on commit: 956c29106abbe3503f57e8a311ee23566488059f