Fixes missing peer dependencies

[eoingroat]

In older npm/yarn setups a peer dependency can be satisfied anywhere to function, and its resolution is ambiguous; however in yarn berry (yarn v2) dependency resolution is strictly and unambiguously enforced.

In yarn berry environments snowflake-connector-nodejs fails to function due to missing peer dependencies; in this case "asn1.js" and "bn.js" are peerDependencies of some of snowflake-connector-nodejs's dependencies. This can be resolved in two ways:

• Making the missing peerDependencies dependencies of snowflake-connector-nodejs
• Making the missing peerDependencies into peerDependencies of snowflake-connector-nodejs (allowing the importing project to satisfy them).

Trying to set them as dependencies of the importing project without setting them as peerDependencies of snowflake-connector-nodejs (the traditional solution) will fail to unambiguously resolve the dependencies (due to broken dependency chain).

This PR resolves the issue with the first fix, that is to resolve the peerDependencies in this project.

[dynamikus]

Any plan to resolve this issue?
bn.js is used
https://github.com/snowflakedb/snowflake-connector-nodejs/blob/master/lib/agent/cert_util.js#L36
yet it dependency is not listed in package.json.
Not sure why the build failed in here but the change is simple.

[onesien]

Just ran into this issue also. Any update?

[danmactough]

Bump. This is also a problem for anyone using this library together with a bundler (like Webpack), as one might do in a Lambda on AWS.

[eoingroat]

I've rebased the branch onto upstream/master.

The tests are failing with:

Run ./ci/test.sh
...
gpg: gcry_kdf_derive failed: Invalid data
gpg: decryption failed: No secret key
Error: Process completed with exit code 2.

I expect it is because a variable is injected on the main branch, or branches owned by project maintainers, that is not present when triggered by myself.

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you 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

---

_{You can retrigger this bot by commenting recheck in this Pull Request}

[eoingroat]

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

[eoingroat]

recheck

[sfc-gh-dszmolka]

this has been fixed in the past with another PR, closing