powershell runner is confused by Unicode curly quote marks

What does this MR do?

It adds two substitutions to the powershell escape code to handle “ and ”.

Why was this MR needed?

Currently if those characters appear in a commit message the runner fails to run the job

What's the best way to test this MR?

commit a change that will be run on a windows powershell runner and include something like “test” in the commit message. It should proceed to run the build.

What are the relevant issue numbers?

Closes #10123