Bump @metamask/utils from 8.4.0 to 8.5.0 (#421)

Bumps [@metamask/utils](https://github.com/MetaMask/utils) from 8.4.0 to
8.5.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/MetaMask/utils/releases"><code>@​metamask/utils</code>'s
releases</a>.</em></p>
<blockquote>
<h2>8.5.0</h2>
<h3>Changed</h3>
<ul>
<li>Bump dependency <code>semver</code> from <code>^5.7.1</code> to
<code>^7.6.0</code> (<a
href="https://redirect.github.com/MetaMask/utils/pull/181">#181</a>).</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Replace dependency <code>superstruct</code> <code>^1.0.3</code> with
ESM-compatible <code>@metamask/superstruct</code> <code>^3.0.0</code>
(<a
href="https://redirect.github.com/MetaMask/utils/pull/185">#185</a>).
<ul>
<li>This fixes the issue of this package being unusable by any
TypeScript project that uses <code>Node16</code> or
<code>NodeNext</code> as its <code>moduleResolution</code> option.</li>
</ul>
</li>
<li>Produce and export ESM-compatible TypeScript type declaration files
in addition to CommonJS-compatible declaration files (<a
href="https://redirect.github.com/MetaMask/utils/pull/182">#182</a>)
<ul>
<li>Previously, this package shipped with only one variant of type
declaration files, and these files were only CommonJS-compatible, and
the <code>exports</code> field in <code>package.json</code> linked to
these files. This is an anti-pattern and was rightfully flagged by the
<a href="https://arethetypeswrong.github.io/">&quot;Are the Types
Wrong?&quot;</a> tool as <a
href="https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseCJS.md">&quot;masquerading
as CJS&quot;</a>. All of the ATTW checks now pass.</li>
</ul>
</li>
<li>Remove chunk files (<a
href="https://redirect.github.com/MetaMask/utils/pull/182">#182</a>).
<ul>
<li>Previously, the build tool we used to generate JavaScript files
extracted common code to &quot;chunk&quot; files. While this was
intended to make this package more tree-shakeable, it also made
debugging more difficult for our development teams. These chunk files
are no longer present.</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/MetaMask/utils/blob/main/CHANGELOG.md"><code>@​metamask/utils</code>'s
changelog</a>.</em></p>
<blockquote>
<h2>[8.5.0]</h2>
<h3>Changed</h3>
<ul>
<li>Bump dependency <code>semver</code> from <code>^5.7.1</code> to
<code>^7.6.0</code> (<a
href="https://redirect.github.com/MetaMask/utils/pull/181">#181</a>).</li>
</ul>
<h3>Fixed</h3>
<ul>
<li>Replace dependency <code>superstruct</code> <code>^1.0.3</code> with
ESM-compatible <code>@metamask/superstruct</code> <code>^3.0.0</code>
(<a
href="https://redirect.github.com/MetaMask/utils/pull/185">#185</a>).
<ul>
<li>This fixes the issue of this package being unusable by any
TypeScript project that uses <code>Node16</code> or
<code>NodeNext</code> as its <code>moduleResolution</code> option.</li>
</ul>
</li>
<li>Produce and export ESM-compatible TypeScript type declaration files
in addition to CommonJS-compatible declaration files (<a
href="https://redirect.github.com/MetaMask/utils/pull/182">#182</a>)
<ul>
<li>Previously, this package shipped with only one variant of type
declaration files, and these files were only CommonJS-compatible, and
the <code>exports</code> field in <code>package.json</code> linked to
these files. This is an anti-pattern and was rightfully flagged by the
<a href="https://arethetypeswrong.github.io/">&quot;Are the Types
Wrong?&quot;</a> tool as <a
href="https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/docs/problems/FalseCJS.md">&quot;masquerading
as CJS&quot;</a>. All of the ATTW checks now pass.</li>
</ul>
</li>
<li>Remove chunk files (<a
href="https://redirect.github.com/MetaMask/utils/pull/182">#182</a>).
<ul>
<li>Previously, the build tool we used to generate JavaScript files
extracted common code to &quot;chunk&quot; files. While this was
intended to make this package more tree-shakeable, it also made
debugging more difficult for our development teams. These chunk files
are no longer present.</li>
</ul>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/MetaMask/utils/commit/c72216b0303b3192dfa41023c6c88f939cde9054"><code>c72216b</code></a>
8.5.0 (<a
href="https://redirect.github.com/MetaMask/utils/issues/191">#191</a>)</li>
<li><a
href="https://github.com/MetaMask/utils/commit/631d1eb641248da441aa78db6e1530d8e4a3e9a6"><code>631d1eb</code></a>
Use <code>@metamask/superstruct</code>, set
<code>moduleResolution</code> to <code>NodeNext</code> (<a
href="https://redirect.github.com/MetaMask/utils/issues/185">#185</a>)</li>
<li><a
href="https://github.com/MetaMask/utils/commit/7eac3c82f3a4a169ee0f7f18b3319827773013bc"><code>7eac3c8</code></a>
Bump semver (<a
href="https://redirect.github.com/MetaMask/utils/issues/181">#181</a>)</li>
<li><a
href="https://github.com/MetaMask/utils/commit/1c408dd664808dffebe5337d983516b0a56df6eb"><code>1c408dd</code></a>
Use <code>ts-bridge</code> for building (<a
href="https://redirect.github.com/MetaMask/utils/issues/182">#182</a>)</li>
<li><a
href="https://github.com/MetaMask/utils/commit/e122e33f4d8935b692c242ff490121469217e115"><code>e122e33</code></a>
Bump tar from 6.1.11 to 6.2.1 (<a
href="https://redirect.github.com/MetaMask/utils/issues/180">#180</a>)</li>
<li>See full diff in <a
href="https://github.com/MetaMask/utils/compare/v8.4.0...v8.5.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@metamask/utils&package-manager=npm_and_yarn&previous-version=8.4.0&new-version=8.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

yarn.lock

@@ -5255,20 +5255,27 @@ __metadata:
   languageName: node
   linkType: hard
 
+"@metamask/superstruct@npm:^3.0.0":
+  version: 3.0.0
+  resolution: "@metamask/superstruct@npm:3.0.0"
+  checksum: 667f8f2947186972516bb72b4ba215eaeede257c8beb0450583dd4c8b00c28729ff938267ca8804a3a351277fd627b8607cafeb71eb7045a2b6930639bb6a341
+  languageName: node
+  linkType: hard
+
 "@metamask/utils@npm:^8.1.0, @metamask/utils@npm:^8.3.0, @metamask/utils@npm:^8.4.0":
-  version: 8.4.0
-  resolution: "@metamask/utils@npm:8.4.0"
+  version: 8.5.0
+  resolution: "@metamask/utils@npm:8.5.0"
   dependencies:
     "@ethereumjs/tx": ^4.2.0
+    "@metamask/superstruct": ^3.0.0
     "@noble/hashes": ^1.3.1
     "@scure/base": ^1.1.3
     "@types/debug": ^4.1.7
     debug: ^4.3.4
     pony-cause: ^2.1.10
     semver: ^7.5.4
-    superstruct: ^1.0.3
     uuid: ^9.0.1
-  checksum: b0397e97bac7192f6189a8625a2dfcb56d3c2cf4dd2cb3d4e012a7e9786f04f59f6917805544bc131a6dacd2c8344e237ae43ad47429bb5eb35c6cf1248440b4
+  checksum: e8eac1c796c3f6b623be3c2736e8682248620f666b180f5c12ce56ee09587d4e28b6811862139a05c7a1bec91415f10ccf0516f3cdf342f88b0189d2a057c24b
   languageName: node
   linkType: hard