chore: update to resolve sec vulnerability in node-forge

[Aaron Wentzel (awentzel)]

Description

Webpack depends on selfsigned which has a vulnerability in 1.10.7. This updates webpack across our solution to use the latest and resolves this vulnerability. Webpack does upgrade to a safe version, with this PR, after running yarn.

Motivation & context

Resolve security vulnerability documented https://github.com/microsoft/fast/network/alert/yarn.lock/node-forge/open and the fix documented webpack/webpack-dev-server#2740

Issue type checklist

• Chore: A change that does not impact distributed packages.
• Bug fix: A change that fixes an issue, link to the issue above.
• New feature: A change that adds functionality.

Is this a breaking change?

• This change causes current functionality to break.

Adding or modifying component(s) in @microsoft/fast-components checklist

• I have added a new component
• I have modified an existing component
• I have updated the definition file
• I have updated the configuration file

Process & policy checklist

• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.