Support for Dataframe mode with parquet

[sfc-gh-dbabbjimenez]

Motivation & Context

JIRA: SNOW-1854994

Description

This pull request includes significant updates to the Demos/demo_pyspark_pipeline.py and Demos/demo_snowpark_pipeline.py files, focusing on the handling of schema and data checkpoints, as well as some minor changes to the snow_connection.py and summary_stats_collector.py files.

Changes to schema and data checkpoints:

• Demos/demo_pyspark_pipeline.py: Added import for CheckpointMode and updated the collect_dataframe_checkpoint function to include a new mode parameter. [1] [2]
• Demos/demo_snowpark_pipeline.py: Updated import statements to include CheckpointMode and validate_dataframe_checkpoint. Replaced check_dataframe_schema_file with validate_dataframe_checkpoint and added a new mode parameter. [1] [2]

Commenting out specific data types:

• Demos/demo_pyspark_pipeline.py: Commented out float, binary, timestamp, and timestamp_ntz data types in the schema and sample data rows. [1] [2] [3]
• Demos/demo_snowpark_pipeline.py: Commented out float, binary, timestamp, and timestamp_ntz data types in the schema and sample data rows. [1] [2]

Minor changes:

• snow_connection.py: Updated the CREATE_STAGE_STATEMENT_FORMAT to remove the TEMPORARY keyword.
• summary_stats_collector.py: Added a newline for better readability.

How Has This Been Tested?

Checklist

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Data correction (data quality issue originating from upstream source or dataset)
• Cleanup and optimization (improvement that does not alter the data returned by a model)
• Other (please specify)
• I attest that this change meets the bar for low risk without security requirements as defined in the Accelerated Risk Assessment Criteria and I have taken the Risk Assessment Training in Workday.
  • Checking this checkbox is mandatory if using the Accelerated Risk Assessment to risk assess the changes in this Pull Request.
  • If this change does not meet the bar for low risk without security requirements (as confirmed by the peer reviewers of this pull request) then a formal Risk Assessment must be completed. Please note that a formal Risk Assessment will require you to spend extra time performing a security review for this change. Please account for this extra time earlier rather than later to avoid unnecessary delays in the release process.

[sfc-gh-fgonzalezmendez]

Please take a look at the comments I left.