SNOW-807303 Use SELECT * EXCLUDE for DataFrame.drop()

[sfc-gh-aalam]

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

   Fixes SNOW-807303

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.

   This PR adds the ability to generate sql using SELECT * EXCLUDE (exclude_cols...) with DataFrame.drop API call.

[sfc-gh-snowflakedb-snyk-sa]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

[sfc-gh-jdu]

is there other functionality that will use this flag?

[sfc-gh-aalam]

yeah. all new query generation improvement for dataframe APIs are protected with this parameter. .distinct(), .random_split(), .stat.sample_by(), .drop() and planning to add .rename() under this.

[sfc-gh-jdu]

is it possible to not check existing names if using exclude? It will trigger a describe query

[sfc-gh-aalam]

as discussed offline, if we don't do this describe query, it may lead to a BCR since SELECT * EXCLUDE (non_existing_column) raises error SQL error while it raises no error today.