Upgrade tough-cookie to 4.3.1 to fix security vulnerability.

[astegmaier]

This addresses #483. There is a security vulnerability in the tough-cookie package for versions <4.3.1 - see https://nvd.nist.gov/vuln/detail/CVE-2023-26136. Previously @azure/ms-rest-js depended on ^3.0.0, which locked tough-cookie to an unsecure version.

Testing

Build (npmrun build) and tests (npm run test) continue to succeed with this upgrade. In addition I reviewed the [release notes for tough-cookie@4.0.0][https://github.com/salesforce/tough-cookie/releases/tag/v4.0.0] (the breaking change from 3.x). Here they are (annotated with [astegmaier]), with why I believe they will not break @azure/ms-rest-js:

• Modernized JS Syntax
  • Use ESLint and Prettier to apply consistent, modern formatting (add dependency on universalify, eslint and prettier) - [astegmaier] eslint and prettier are devDependencies of tough-cookie so they shouldn't break consumers. universalify seems to be aimed at backward-compatible usage
• Upgraded version dependencies for psl and async - [astegmaier] async is a devDependency of tough-cookie, so an upgrade shouldn't break consumers. psl also seems to be a pretty benign dependency
• Re-order parameters for findCookies() - callback fn has to be last in order to comply with universalify [astegmaier] it doesn't look like @azure/ms-rest-js uses findCookies anywhere`
• Use Classes instead of function prototypes to define classes
  • Might break people using .call() to do inheritance using function prototypes - [astegmaier] it doesn't look like `@azurems-rest-js uses this pattern anywhere

[xirzec]

Closing in favor of #485