fix value escaping in codeql-env.sh

[hmakholm]

CodeQL itself complained (correctly) that the escaping here would fail if the value contains backslashes.

Switch to single-quoting, which is less tricky to escape.

Hmmm, how confident are we that there are not consumers that try to parse codeql-env.sh themselves and will break if they don't find double quotes? They should be using the JSON output instead, but still ...

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.

[aeisenberg]

Suggested change

	([key,value])=>"export "+key+"='"+value.replace(/'/g,"'\"'\"'")+"'"
	([key,value])=>`export ${key}='${value.replace(/'/g,"'\"'\"'")}'`

[aeisenberg]

Yes, it's safer to use single quotes instead of escaping the $.

[alexet]

I know there are consumers converting the windows output to sh (as they use bash on windows) but I don't know about users converting the sh output.

[aeisenberg]

Arrrrgh....also need to update the compile files. Let me just push a change up.

[hmakholm]

Do we need a change note warning users of the different quoting?

[aeisenberg]

Based on how we are doing things now, the answer is no. And as we discussed, this might change, but I don't think we should be holding this PR up until we make any process changes.

[aeisenberg]

@hmakholm, merged this for you because you mentioned earlier that you kept having merge conflicts if you waited too long.

[hmakholm]

Thank you!