SNOW-2331878: auto release branch preparation

[sfc-gh-aling]

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

   Fixes SNOW-NNNNNNN

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.

   Please write a short description of how your code change solves the related issue.

[sfc-gh-aling]

@sfc-gh-heshah , how long would it take to implement a python based unparser?

[sfc-gh-heshah]

I would wager at most one week. If you take a look at the server-side Snowpark Unparser for guidance on output format, and the server-side Snowpark decoder for how to work with protobufs in Python, they're both extremely straightforward.

[sfc-gh-joshi]

I have my own repository root named snowpandas, though it's not a big deal if I need to temporarily edit the script before running it. Not sure what a more robust solution is (maybe checking git remote get-url origin matches this repo, then comparing git rev-parse --show-toplevel to the cwd?)

[sfc-gh-aling]

feel free to contribute to this script!