SNOW-3259059: Avoid server-side bug by using CHR(34) instead of lit('"') in concat

[sfc-gh-helmeleegy]

1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-3259059

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
     • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency
   • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
   • I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines
   • If adding any arguments to public Snowpark APIs or creating new public Snowpark APIs, I acknowledge that I have ensured my changes include AST support. Follow the link for more information: AST Support Guidelines

3. Please describe how your code solves the related issue.

   Fix a Snowflake platform compatibility issue (SNOW-3259059) where concat(lit('"'), ...) could lose the leading quote through some EXCEPT / chained set-operation plans by lowering that literal to CHR(34) in generated SQL.

[sfc-gh-joshi]

@sfc-gh-helmeleegy Do you know what exactly the root cause of the bug here is, and why this workaround is valid? The linked JIRA isn't very clear about it.

Is the bug also present if the concatenated literal has more than just the single double-quote character, like concat(lit('""""xxxxx'), "column")?

[sfc-gh-joshi]

Should we combine these into a single list comprehension?

[sfc-gh-helmeleegy]

Done.

[sfc-gh-helmeleegy]

@sfc-gh-helmeleegy Do you know what exactly the root cause of the bug here is, and why this workaround is valid? The linked JIRA isn't very clear about it.

Is the bug also present if the concatenated literal has more than just the single double-quote character, like concat(lit('""""xxxxx'), "column")?

The exact root cause on the server side is not clear (to us at least). I'm trying to work with the SQL's team oncall to understand when a mitigation is expected from their side. This PR is meant to unblock the customer using a client-side fix to the issue they faced.

[sfc-gh-mayliu]

LGTM, thanks for fixing this