chore: Move test/dev tools to devDependencies

[Gudahtt]

Development & PR Process

1. Follow MetaMask Mobile Coding Standards
2. Add release-xx label to identify the PR slated for a upcoming release (will be used in release discussion)
3. Add needs-dev-review label when work is completed
4. Add needs-qa label when dev review is completed
5. Add QA Passed label when QA has signed off

Description

Packages used solely for development tools and testing have been moved from dependencies to devDependencies.

Issue

None

Checklist

• There is a related GitHub issue
• Tests are included if applicable
• Any added code is fully documented

[Cal-L]

LGTM

[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: semver@4.3.6, semver@5.3.0, semver@5.4.1, semver@5.7.1, semver@6.3.0, semver@7.0.0, semver@7.3.5, semver@7.3.7, semver@7.3.8, semver@7.5.0, semver@7.5.1

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

[Gudahtt]

@SocketSecurity ignore semver@4.3.6
@SocketSecurity ignore semver@5.3.0
@SocketSecurity ignore semver@5.4.1
@SocketSecurity ignore semver@5.7.1
@SocketSecurity ignore semver@6.3.0
@SocketSecurity ignore semver@7.0.0
@SocketSecurity ignore semver@7.3.5
@SocketSecurity ignore semver@7.3.7
@SocketSecurity ignore semver@7.3.8
@SocketSecurity ignore semver@7.5.0
@SocketSecurity ignore semver@7.5.1

False positive, that package isn't being added by this PR

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information