SNOW-1480718: Support Series.str.translate

[sfc-gh-joshi]

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

   Fixes SNOW-1480718

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.

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

This PR implements Series.str.translate using SQL TRANSLATE.

Unlike the native pandas version, we cannot perform one-to-many character mappings with SQL TRANSLATE. I considered using chained REPLACE calls to mimic this behavior, but that would cause discrepancies in situations where one REPLACE mapping generates entries that match the replacement keys of a subsequent REPLACE calls. As such, for these use cases it is recommended for users to manually chain Series.str.replace calls as necessary.

Slack thread discussing future work on a more robust multi-character approach using REPLACE with sentinel values: https://snowflake.slack.com/archives/C04HF38JFAQ/p1718388095381469

[sfc-gh-mvashishtha]

some minor comments

[sfc-gh-helmeleegy]

LGTM. Thanks, Jonathan! Can you please update the PR description to better describe the plan for supporting multi-characters in the future? You can give a short description and point to the slack thread for more details.

[sfc-gh-mvashishtha]

nice work!