SNOW-1491028 : Snowflake JDBC Driver 4.2 compliant issue.

[sfc-gh-ext-simba-vb]

Overview

SNOW-1491028

Pre-review self checklist

• PR branch is updated with all the changes from master branch
• The code is correctly formatted (run mvn -P check-style validate)
• New public API is not unnecessary exposed (run mvn verify and inspect target/japicmp/japicmp.html)
• The pull request name is prefixed with SNOW-XXXX:
• Code is in compliance with internal logging requirements

External contributors - please answer these questions before submitting a pull request. Thanks!

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

   Issue: #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 modifying authorization mechanisms
   • I am adding new credentials
   • I am modifying OCSP code
   • I am adding a new dependency or upgrading an existing one
   • I am adding new public/protected component not marked with @SnowflakeJdbcInternalApi (note that public/protected methods/fields in classes marked with this annotation are already internal)

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

Issue 1016 - https://github.com/snowflakedb/snowflake-sdks-drivers-issues-teamwork/issues/1016

1. Currently the setHoldability method always throws the exception. According to the docs we should throw the exception only when the given holdability is no supported - in other cases it should be no-op.
   Now Driver will throw SnowflakeLoggedFeatureNotSupportedException only when holdability parameter is HOLD_CURSORS_OVER_COMMIT
2. If the connection is closed or given value is outside of the possible range in the standard, the driver will throw SQLException.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

1 out of 2 committers have signed the CLA.
✅ (sfc-gh-ext-simba-vb)[https://github.com/sfc-gh-ext-simba-vb]
❌ @Vikramsinh.Barbade
Vikramsinh.Barbade seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[sfc-gh-ext-simba-vb]

I have read the CLA Document and I hereby sign the CLA