chore(deps-dev): bump esbuild from 0.15.6 to 0.15.7 (#201)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.15.6 to 0.15.7.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/releases">esbuild's releases</a>.</em></p>
<blockquote>
<h2>v0.15.7</h2>
<ul>
<li>
<p>Add <code>--watch=forever</code> to allow esbuild to never terminate (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1511">#1511</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1885">#1885</a>)</p>
<p>Currently using esbuild's watch mode via <code>--watch</code> from the CLI will stop watching if stdin is closed. The rationale is that stdin is automatically closed by the OS when the parent process exits, so stopping watch mode when stdin is closed ensures that esbuild's watch mode doesn't keep running forever after the parent process has been closed. For example, it would be bad if you wrote a shell script that did <code>esbuild --watch &amp;</code> to run esbuild's watch mode in the background, and every time you run the script it creates a new <code>esbuild</code> process that runs forever.</p>
<p>However, there are cases when it makes sense for esbuild's watch mode to never exit. One such case is within a short-lived VM where the lifetime of all processes inside the VM is expected to be the lifetime of the VM. Previously you could easily do this by piping the output of a long-lived command into esbuild's stdin such as <code>sleep 999999999 | esbuild --watch &amp;</code>. However, this possibility often doesn't occur to people, and it also doesn't work on Windows. People also sometimes attempt to keep esbuild open by piping an infinite stream of data to esbuild such as with <code>esbuild --watch &lt;/dev/zero &amp;</code> which causes esbuild to spin at 100% CPU. So with this release, esbuild now has a <code>--watch=forever</code> flag that will not stop watch mode when stdin is closed.</p>
</li>
<li>
<p>Work around <code>PATH</code> without <code>node</code> in install script (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2519">#2519</a>)</p>
<p>Some people install esbuild's npm package in an environment without the <code>node</code> command in their <code>PATH</code>. This fails on Windows because esbuild's install script runs the <code>esbuild</code> command before exiting as a sanity check, and on Windows the <code>esbuild</code> command has to be a JavaScript file because of some internal details about how npm handles the <code>bin</code> folder (specifically the <code>esbuild</code> command lacks the <code>.exe</code> extension, which is required on Windows). This release attempts to work around this problem by using <code>process.execPath</code> instead of <code>&quot;node&quot;</code> as the command for running node. In theory this means the installer can now still function on Windows if something is wrong with <code>PATH</code>.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/evanw/esbuild/blob/master/CHANGELOG.md">esbuild's changelog</a>.</em></p>
<blockquote>
<h2>0.15.7</h2>
<ul>
<li>
<p>Add <code>--watch=forever</code> to allow esbuild to never terminate (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1511">#1511</a>, <a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/1885">#1885</a>)</p>
<p>Currently using esbuild's watch mode via <code>--watch</code> from the CLI will stop watching if stdin is closed. The rationale is that stdin is automatically closed by the OS when the parent process exits, so stopping watch mode when stdin is closed ensures that esbuild's watch mode doesn't keep running forever after the parent process has been closed. For example, it would be bad if you wrote a shell script that did <code>esbuild --watch &amp;</code> to run esbuild's watch mode in the background, and every time you run the script it creates a new <code>esbuild</code> process that runs forever.</p>
<p>However, there are cases when it makes sense for esbuild's watch mode to never exit. One such case is within a short-lived VM where the lifetime of all processes inside the VM is expected to be the lifetime of the VM. Previously you could easily do this by piping the output of a long-lived command into esbuild's stdin such as <code>sleep 999999999 | esbuild --watch &amp;</code>. However, this possibility often doesn't occur to people, and it also doesn't work on Windows. People also sometimes attempt to keep esbuild open by piping an infinite stream of data to esbuild such as with <code>esbuild --watch &lt;/dev/zero &amp;</code> which causes esbuild to spin at 100% CPU. So with this release, esbuild now has a <code>--watch=forever</code> flag that will not stop watch mode when stdin is closed.</p>
</li>
<li>
<p>Work around <code>PATH</code> without <code>node</code> in install script (<a href="https://github-redirect.dependabot.com/evanw/esbuild/issues/2519">#2519</a>)</p>
<p>Some people install esbuild's npm package in an environment without the <code>node</code> command in their <code>PATH</code>. This fails on Windows because esbuild's install script runs the <code>esbuild</code> command before exiting as a sanity check, and on Windows the <code>esbuild</code> command has to be a JavaScript file because of some internal details about how npm handles the <code>bin</code> folder (specifically the <code>esbuild</code> command lacks the <code>.exe</code> extension, which is required on Windows). This release attempts to work around this problem by using <code>process.execPath</code> instead of <code>&quot;node&quot;</code> as the command for running node. In theory this means the installer can now still function on Windows if something is wrong with <code>PATH</code>.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/c0b8a538c2bf5106977895535010ec402cae75f8"><code>c0b8a53</code></a> publish 0.15.7 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/976b57a5700165ff465a9a932e6a101ab6e151ee"><code>976b57a</code></a> validate <code>await</code> in shorthand destructuring</li>
<li><a href="https://github.com/evanw/esbuild/commit/8ac75295183f1a0a368866ebbf330c3883a959ff"><code>8ac7529</code></a> tests: ignore new top-level await test262 tests</li>
<li><a href="https://github.com/evanw/esbuild/commit/dbd21a861ae9618faf03e1965986154052224351"><code>dbd21a8</code></a> tests: skip new features in test262</li>
<li><a href="https://github.com/evanw/esbuild/commit/7331a348c66380be6e0d0725e85c6565f32b1c43"><code>7331a34</code></a> ci: upgrade to yarn 3.2.3, enable more tests</li>
<li><a href="https://github.com/evanw/esbuild/commit/31e1cee49e70a2c1de6158b5a9f5aab5ac99c5ed"><code>31e1cee</code></a> install script: tiny wasm tree-shaking improvement</li>
<li><a href="https://github.com/evanw/esbuild/commit/0438f643e25563566431d282a9e8b13607c68ce7"><code>0438f64</code></a> ci: run deno tests on windows</li>
<li><a href="https://github.com/evanw/esbuild/commit/7549073c2fe6f0d2f72f9849c0c09a0e189303fc"><code>7549073</code></a> ci: pin deno version to avoid test flakes</li>
<li><a href="https://github.com/evanw/esbuild/commit/6a26f5926fdd4b18d09a55c4a4cee9fcba41b737"><code>6a26f59</code></a> tests: use unused test in <code>node-unref-tests</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/037ffbba5928d858115c4e4c02eb71ba230753ca"><code>037ffbb</code></a> tests: remove <code>source-map</code> from <code>js-api-tests</code></li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.15.6...v0.15.7">compare view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.15.6&new-version=0.15.7)](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 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>

Author: dependabot[bot]