resolutions for yarn.lock pinned packages

[dlpzx]

Feature or Bugfix

• Bugfix

Detail

yarn.lock and package-lock.json react differently when defining specific versions for a package in package.json

• yarn.lock works when the pinned packages are added to the resolutions section
• package-lock.json when they are in the overrides section

When generating each of these accommodate the package.json accordingly.

Relates

Dependabot and npm audit

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

• Does this PR introduce or modify any input fields or queries - this includes
  fetching data from storage outside the application (e.g. a database, an S3 bucket)?
  • Is the input sanitized?
  • What precautions are you taking before deserializing the data you consume?
  • Is injection prevented by parametrizing queries?
  • Have you ensured no eval or similar functions are used?
• Does this PR introduce any functionality or component that requires authorization?
  • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  • Are you logging failed auth attempts?
• Are you using or adding any cryptographic features?
  • Do you use a standard proven implementations?
  • Are the used keys controlled by the customer? Where are they stored?
• Are you introducing any new policies/roles/users?
  • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[noah-paige]

Tested this in an AWS Deployment - frontend built properly and all looks good

Approving!