Bump node-forge package version

[jportner]

We have a direct dependency on node-forge 0.9.1, and a also a transitive dependency via:

@elastic/request-crypto@1.1.4 > node-jose@1.1.0 > node-forge@0.7.6

This commit updates both of these to 0.10.0.

Note: we still have a transitive dev dependency on node-forge 0.9.0; that package is out of date so I opted not to try to bump the version.

[jportner]

Note: I did a manual smoke test by running Kibana and parsing a PKCS12 keystore, which is what we use node-forge for. All worked fine.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 17985c3

Build metrics

async chunks size

id	value	diff	baseline
enterpriseSearch	372.4KB	+37.0B	372.4KB

page load bundle size

id	value	diff	baseline
upgradeAssistant	64.7KB	+37.0B	64.6KB

oss distributable file count

id	value	diff	baseline
total	27235	-58	27293

distributable file count

id	value	diff	baseline
total	45411	-58	45469

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[jportner]

I forgot to mention before the review, but just for posterity:
There are no breaking changes between 0.7.6 and 0.9.1. In addition, node-jose's usage of node-forge did not include any of the vulnerable methods that were removed in 0.10.0. Finally, I followed node-jose's commit history (its master branch is using a newer version of node-forge); all of their updates to node-forge did not require any code updates. So that's how I deemed it was safe to force this to resolve to 0.10.0.