SNOW-2173685 respect existing param control of using SCOPED keyword f…

[sfc-gh-zyao]

…or sproc

Description

• respect existing param control of using SCOPED keyword for sproc
  • currently whether to use scoped keyword for sproc is controlled by the parameter ENABLE_FIX_1375538, and this change makes sure we respect that
  • the change is effectively no-op for non-sproc because with or without SCOPED keyword, they will use session-scoped temp objects when writing pandas.
  • for Snowflake reviewers, more details about this decision is covered in this doc

Testing

• existing tests to make sure this change does not break anything
• manual testing to make sure this is working for sproc
  • when we enable ENABLE_FIX_1375538, we see a job-scoped temp object is created
    
  • when we disable ENABLE_FIX_1375538, we are not seeing job-scoped temp object. Instead, we see session-scoped temp, which remains valid even beyond sproc
    

Please answer these questions before submitting your pull requests. Thanks!

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

   Fixes #NNNN

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am modifying authorization mechanisms
   • I am adding new credentials
   • I am modifying OCSP code
   • I am adding a new dependency

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

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

4. (Optional) PR for stored-proc connector:

[sfc-gh-sfan]

Let's add a note to remove this with a BCR from the server side to make these temp objects job scoped.

Also, let's use a more meaning variable name to represent ENABLE_FIX_1375538. We should verify if this param can be fetched outside of sp. I suspect not and this might just be a pure no-op outside of sp.