SNOW-2331021: Wrap internal Series/DF creation

[sfc-gh-joshi]

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

   Fixes SNOW-2331021

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.

Many internal functions create an instance of pd.Series or pd.DataFrame, then retrieve a query compiler from the object. With hybrid execution enabled, this query compiler is sometimes an instance of NativeQueryCompiler, which may break invariants when a SnowflakeQueryCompiler is expected instead. The new helper function new_snow_series and new_snow_df disable hybrid mode when creating a Series/DF for internal use.

This PR replaces constructor calls within the SFQC and indexing_overrides, which were responsible for the bug in the original ticket. Other constructor calls remain, but I have not yet triaged them.

This removes a few hundred test failures in modin_hybrid_integ_results.csv.

[sfc-gh-jkew]

Why did you need to rebuild the csv? Not complaining I just want to make sure that is not a regular occurance.

[sfc-gh-joshi]

Why did you need to rebuild the csv? Not complaining I just want to make sure that is not a regular occurance.

Since this test was fixing a hybrid-specific bug, I wanted to see if the number of failures was reduced. It may help if we sort the DF on test name before exporting the CSV so the diff is less messy.

[sfc-gh-jkew]

Why did you need to rebuild the csv? Not complaining I just want to make sure that is not a regular occurance.

Since this test was fixing a hybrid-specific bug, I wanted to see if the number of failures was reduced. It may help if we sort the DF on test name before exporting the CSV so the diff is less messy.

Ahh, I see now in the description: " few hundred test failures" that's awesome.

[sfc-gh-joshi]

Why did you need to rebuild the csv? Not complaining I just want to make sure that is not a regular occurance.

Since this test was fixing a hybrid-specific bug, I wanted to see if the number of failures was reduced. It may help if we sort the DF on test name before exporting the CSV so the diff is less messy.

Ahh, I see now in the description: " few hundred test failures" that's awesome.

Just to be clear, I didn't check which tests were fixed, I just compared the output of wc -l tests/integ/modin/modin_hybrid_integ_results.csv before (20706) and after (20191) this PR.

I just now sorted and dropped the position index of CSV, so diffs should be smaller in the future.