move json-rpc-engine from merged-packages to packages

[kanthesha]

Explanation

In the process of migrating json-rpc-engine into core monorepo. In this PR we are moving json-rpc-engine from merged-packages to packages folder.

In this process, we followed below steps.
Moving to packages

1. Move migration target from merged-packages/ to packages/.
2. Run yarn install in the root directory.
3. Check that all tests are passing in migration target by running yarn workspace @metamask/json-rpc-engine test.

Update downstream repos

1. Bump the json-rpc-engine to 7.2.0 in root and packages
2. Added references in tsconfig.json and tsconfig.build.json

Lints and Constraints

1. Fixed yarn constraints errors
2. Applied yarn workspace @metamask/json-rpc-engine changelog:validate

References

• Closes Moving json-rpc-engine from merged-packages into the packages #1919

Changelog Changes

@metamask/eth-json-rpc-provider

• CHANGED: Bump dependency on @metamask/json-rpc-engine to ^7.2.0

@metamask/json-rpc-engine

• CHANGED: Bump dependency on @metamask/utils to ^8.2.0

@metamask/network-controller

• CHANGED: Bump dependency on @metamask/json-rpc-engine to ^7.2.0

@metamask/permission-controller

• CHANGED: Bump dependency on @metamask/json-rpc-engine to ^7.2.0

@metamask/queued-request-controller

• CHANGED: Bump dependency on @metamask/json-rpc-engine to ^7.2.0

@metamask/selected-network-controller

• CHANGED: Bump dependency on @metamask/json-rpc-engine to ^7.2.0

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]

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

🚮 Removed packages: @types/jest@29.5.7

[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.

[MajorLift]

I've finished testing the tag porting script, and I think it will be safer to run it before the package is moved out of merged-packages/.

So #1802 will need to be merged before this PR can be merged. Sorry for the confusion!

[MajorLift]

Tags have been successfully ported to core!

• Example tag diff link from CHANGELOG: https://github.com/MetaMask/core/compare/json-rpc-engine@6.1.0...@metamask/json-rpc-engine@7.0.0
• Verify full list with this command:

git ls-remote --tags origin | grep 'json-rpc-engine'

[MajorLift]

Note: Some earlier release commits that were untagged in the original repo have been skipped by the tag porting script, and will be tagged manually.

• TODO: GitHub may show these manually-created tags out of order due to sorting by tag creation date instead of release commit timestamp.

[FrederikBolding]

Reviewed PermissionController diff

[FrederikBolding]

Why is this package being downgraded?

[MajorLift]

Thanks for catching this! I just pushed a fix.

I'll add an entry in the migration checklist to double-check for dependency version bumps or other changes in main that may have happened while the PR is open.

For future migrations, we plan to coordinate to minimize the time these PRs are kept open so there's less chance of something like this slipping through.

Found something

[mcmire]

I updated the PR description to mention the dependency changes to other packages being made here. This looks good.