json-rpc-engine: Update tsconfig*.json, typedoc.json, jest.config.js to align with repo defaults

[kanthesha]

Explanation

In the process of migrating json-rpc-engine to core monorepo. In this PR, we have updated tsconfig*.json, typedoc.json, jest.config.js to extend from corresponding files in the core root directory.

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate

[mcmire]

I tested this with a branch that brings json-rpc-engine into packages/, and this seems to work.

[MajorLift]

fb81f3b needs to be reverted.

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
New author	@metamask/eth-simple-keyring	5.1.1	New Author: lgbot Previous Author: metamaskbot	@metamask/[email protected] via package.json @metamask/[email protected] via packages/accounts-controller/package.json @metamask/[email protected] via packages/keyring-controller/package.json @metamask/[email protected] via packages/signature-controller/package.json
Unstable ownership	@metamask/eth-simple-keyring	5.1.1	Author: lgbot	@metamask/[email protected] via package.json @metamask/[email protected] via packages/accounts-controller/package.json @metamask/[email protected] via packages/keyring-controller/package.json @metamask/[email protected] via packages/signature-controller/package.json

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore @metamask/[email protected]

[MajorLift]

LGTM!