fix windows bat execution

[faulycoelho]

Fixes #1706
In the workflow for windows environment exist a process to append '^' three times before every single char, this is preventing correct execution.
After the correction, the dotnet sonarscanner end works well.

[pavel-mikula-sonarsource]

Hi @faulycoelho,

Can you please create a new issue first, with full description, and with the mention of the old one? The old issue is closed.

[csaba-sagi-sonarsource]

Tests required.

[faulycoelho]

Hi @faulycoelho,

Can you please create a new issue first, with full description, and with the mention of the old one? The old issue is closed.

Done: #1706

[faulycoelho]

Tests required.

Tests created, committed.

[costin-zaharia-sonarsource]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s), but failed to run 1 pipeline(s).

[martin-strecker-sonarsource]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s), but failed to run 1 pipeline(s).

[faulycoelho]

Fixed testing and escaping to use '^^^' like the previous version, but only with special characters.

[martin-strecker-sonarsource]

Hello @faulycoelho
I took a look into this strange behavior and tried to reproduce the exact problem here #1751, here #1752, and here #1765. We still do not fully understand what is causing the problem on your side. As far as I can tell, it is related to a different behavior between Java 17 and Java 11 with respect to argument handling.
We need to add proper tests like in #1765 in place first before we can fix the issue like in #1751. Thank you for pointing us in the right direction, but as long as we do not know what exact string pattern is causing the problem and how we deal with it, we will need to stick to the current escaping mechanism for the moment. See also my comment here regarding the possible root cause.