[sitecore-jss-dev-tools][sitecore-jss-cli] Replace old and security vulnerable 'request' NPM package with axios

[illiakovalenko]

Description

• Replaced request by axios
• Added additional unit tests for package-deploy.ts
• Used axios transport in order to apply cert pinning. Currently axios doesn't support socket events - More flexible ways to customize adapters axios/axios#2808 (comment)

Motivation

How Has This Been Tested?

• Some unit tests
• Manually

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update (non-breaking change; modified files are limited to the /docs directory)

Checklist:

• I have read the Contributing guide.
• My code follows the code style of this project.
• My code/comments/docs fully adhere to the Code of Conduct.
• My change is a code change and it requires an update to the documentation.
• My change is a documentation change and it requires an update to the navigation.

[ambrauer]

Looks great. Think we need to upgrade the other packages' axios versions (see comment), but otherwise just a couple other minor comments.

[nickwesselman]

Hey @illiakovalenko! Can you confirm that this will work with NODE_EXTRA_CA_CERTS?

Edit: We realized later that this environment variable can't be set with dotenv anyway. I know it's not technically in scope of this, but could we potentially add our own environment variable for configuring the ca on our https agent?

https://medium.com/@jamomani/adding-trusted-ca-to-node-client-with-axios-2792024bca4
https://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/node-registering-certs.html

cc @anastasiya29 @ambrauer

Edit again: Nevermind, let's take care of this elsewhere so you can merge.