Migrate eth-json-rpc-provider into core monorepo (1/2)

[MajorLift]

Explanation

This is the first of two PRs that will migrate eth-json-rpc-provider into the core monorepo by following these steps: #1079 (comment).

• This PR focuses on migrating the git history of the original package.
  • eth-json-rpc-provider is moved into a temporary directory in core (merged-packages/) with git history fully intact.
  • This PR will be merged without squashing to preserve the git history.
• The second PR will remove the merged-packages/ directory and integrate eth-json-rpc-provider into the packages/ directory, resolving any issues arising from applying core monorepo linter/compiler/build settings to the newly added package.

Blocked by

• 2.2.0 eth-json-rpc-provider#29

References

• Partially implements Fully migrate eth-json-rpc-provider into core monorepo  #1551
• See Align ESLint, Prettier packages and configs with core monorepo ahead of migration eth-json-rpc-provider#28 for preparatory steps taken in original repo.

Changelog

N/A since @metamask/eth-json-rpc-provider isn't usable from the monorepo as of this PR.

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

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/auto-changelog	3.1.0	None	+0	166 kB	metamaskbot
eslint-config-prettier	8.5.0	None	+9	1.21 MB	lydell
jest	28.1.3	None	+122	14.1 MB	simenb
ts-jest	28.0.8	None	+123	14.3 MB	kul
@types/jest	28.1.8	eval	+26	2.84 MB	types
prettier-plugin-packagejson	2.4.5	None	+4	15.9 MB	matzkoh
@types/node	17.0.23	None	+0	1.68 MB	types
depcheck	1.4.3	filesystem	+54	17.4 MB	rumpl
prettier	2.7.1	None	+0	15.8 MB	prettier-bot
typedoc	0.23.28	network	+7	11.3 MB	typedoc-bot
eslint-plugin-jest	27.1.5	None	+16	2.96 MB	simenb

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: react-is@18.2.0, @babel/plugin-syntax-class-properties@7.10.4, @lavamoat/aa@3.1.5, cosmiconfig@7.1.0, shiki@0.11.1, vscode-oniguruma@1.6.2

Next steps

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 foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

[MajorLift]

@SocketSecurity ignore-all

All packages are current with main branch.

[mcmire]

Looks good!

[Gudahtt]

LGTM!