build(deps): bump esbuild from 0.25.8 to 0.25.11 (#423)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.25.8 to
0.25.11.
<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.25.11</h2>
<ul>
<li>
<p>Add support for <code>with { type: 'bytes' }</code> imports (<a
href="https://redirect.github.com/evanw/esbuild/issues/4292">#4292</a>)</p>
<p>The <a href="https://github.com/tc39/proposal-import-bytes">import
bytes</a> proposal has reached stage 2.7 in the TC39 process, which
means that although it isn't quite recommended for implementation, it's
generally approved and ready for validation. Furthermore it has already
been implemented by <a
href="https://docs.deno.com/examples/importing_bytes/">Deno</a> and <a
href="https://redirect.github.com/webpack/webpack/pull/19928">Webpack</a>.
So with this release, esbuild will also add support for this. It behaves
exactly the same as esbuild's existing <a
href="https://esbuild.github.io/content-types/#binary"><code>binary</code>
loader</a>. Here's an example:</p>
<pre lang="js"><code>import data from './image.png' with { type: 'bytes'
}
const view = new DataView(data.buffer, 0, 24)
const width = view.getInt32(16)
const height = view.getInt32(20)
console.log('size:', width + '\xD7' + height)
</code></pre>
</li>
<li>
<p>Lower CSS media query range syntax (<a
href="https://redirect.github.com/evanw/esbuild/issues/3748">#3748</a>,
<a
href="https://redirect.github.com/evanw/esbuild/issues/4293">#4293</a>)</p>
<p>With this release, esbuild will now transform CSS media query range
syntax into equivalent syntax using <code>min-</code>/<code>max-</code>
prefixes for older browsers. For example, the following CSS:</p>
<pre lang="css"><code>@media (640px &lt;= width &lt;= 960px) {
  main {
    display: flex;
  }
}
</code></pre>
<p>will be transformed like this with a target such as
<code>--target=chrome100</code> (or more specifically with
<code>--supported:media-range=false</code> if desired):</p>
<pre lang="css"><code>@media (min-width: 640px) and (max-width: 960px) {
  main {
    display: flex;
  }
}
</code></pre>
</li>
</ul>
<h2>v0.25.10</h2>
<ul>
<li>
<p>Fix a panic in a minification edge case (<a
href="https://redirect.github.com/evanw/esbuild/issues/4287">#4287</a>)</p>
<p>This release fixes a panic due to a null pointer that could happen
when esbuild inlines a doubly-nested identity function and the final
result is empty. It was fixed by emitting the value
<code>undefined</code> in this case, which avoids the panic. This case
must be rare since it hasn't come up until now. Here is an example of
code that previously triggered the panic (which only happened when
minifying):</p>
<pre lang="js"><code>function identity(x) { return x }
identity({ y: identity(123) })
</code></pre>
</li>
<li>
<p>Fix <code>@supports</code> nested inside pseudo-element (<a
href="https://redirect.github.com/evanw/esbuild/issues/4265">#4265</a>)</p>
<p>When transforming nested CSS to non-nested CSS, esbuild is supposed
to filter out pseudo-elements such as <code>::placeholder</code> for
correctness. The <a href="https://www.w3.org/TR/css-nesting-1/">CSS
nesting specification</a> says the following:</p>
<blockquote>
<p>The nesting selector cannot represent pseudo-elements (identical to
the behavior of the ':is()' pseudo-class). We’d like to relax this
restriction, but need to do so simultaneously for both ':is()' and
'&amp;', since they’re intentionally built on the same underlying
mechanisms.</p>
</blockquote>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's
changelog</a>.</em></p>
<blockquote>
<h2>0.25.11</h2>
<ul>
<li>
<p>Add support for <code>with { type: 'bytes' }</code> imports (<a
href="https://redirect.github.com/evanw/esbuild/issues/4292">#4292</a>)</p>
<p>The <a href="https://github.com/tc39/proposal-import-bytes">import
bytes</a> proposal has reached stage 2.7 in the TC39 process, which
means that although it isn't quite recommended for implementation, it's
generally approved and ready for validation. Furthermore it has already
been implemented by <a
href="https://docs.deno.com/examples/importing_bytes/">Deno</a> and <a
href="https://redirect.github.com/webpack/webpack/pull/19928">Webpack</a>.
So with this release, esbuild will also add support for this. It behaves
exactly the same as esbuild's existing <a
href="https://esbuild.github.io/content-types/#binary"><code>binary</code>
loader</a>. Here's an example:</p>
<pre lang="js"><code>import data from './image.png' with { type: 'bytes'
}
const view = new DataView(data.buffer, 0, 24)
const width = view.getInt32(16)
const height = view.getInt32(20)
console.log('size:', width + '\xD7' + height)
</code></pre>
</li>
<li>
<p>Lower CSS media query range syntax (<a
href="https://redirect.github.com/evanw/esbuild/issues/3748">#3748</a>,
<a
href="https://redirect.github.com/evanw/esbuild/issues/4293">#4293</a>)</p>
<p>With this release, esbuild will now transform CSS media query range
syntax into equivalent syntax using <code>min-</code>/<code>max-</code>
prefixes for older browsers. For example, the following CSS:</p>
<pre lang="css"><code>@media (640px &lt;= width &lt;= 960px) {
  main {
    display: flex;
  }
}
</code></pre>
<p>will be transformed like this with a target such as
<code>--target=chrome100</code> (or more specifically with
<code>--supported:media-range=false</code> if desired):</p>
<pre lang="css"><code>@media (min-width: 640px) and (max-width: 960px) {
  main {
    display: flex;
  }
}
</code></pre>
</li>
</ul>
<h2>0.25.10</h2>
<ul>
<li>
<p>Fix a panic in a minification edge case (<a
href="https://redirect.github.com/evanw/esbuild/issues/4287">#4287</a>)</p>
<p>This release fixes a panic due to a null pointer that could happen
when esbuild inlines a doubly-nested identity function and the final
result is empty. It was fixed by emitting the value
<code>undefined</code> in this case, which avoids the panic. This case
must be rare since it hasn't come up until now. Here is an example of
code that previously triggered the panic (which only happened when
minifying):</p>
<pre lang="js"><code>function identity(x) { return x }
identity({ y: identity(123) })
</code></pre>
</li>
<li>
<p>Fix <code>@supports</code> nested inside pseudo-element (<a
href="https://redirect.github.com/evanw/esbuild/issues/4265">#4265</a>)</p>
<p>When transforming nested CSS to non-nested CSS, esbuild is supposed
to filter out pseudo-elements such as <code>::placeholder</code> for
correctness. The <a href="https://www.w3.org/TR/css-nesting-1/">CSS
nesting specification</a> says the following:</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/evanw/esbuild/commit/6b7c4f2dcbcaa1238bca0f7a4a1d95918296c82e"><code>6b7c4f2</code></a>
publish 0.25.11 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/7295c1aebc8d4f42eed08aa008cc0d7ec617727d"><code>7295c1a</code></a>
css: also parse media queries in <code>@import</code> rules</li>
<li><a
href="https://github.com/evanw/esbuild/commit/e3991dd25ab7422981bd6006a5a8c6f741699105"><code>e3991dd</code></a>
css: some adjustments to <code>@import</code> parsing</li>
<li><a
href="https://github.com/evanw/esbuild/commit/8bb82cad6be9e51d44e98640618c56964188adbd"><code>8bb82ca</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3748">#3748</a>,
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/4293">#4293</a>:
lower css media range syntax</li>
<li><a
href="https://github.com/evanw/esbuild/commit/d8c3f879ce9a4cfdf6ce97e0dc1163a816fc30dd"><code>d8c3f87</code></a>
css: parse and print media queries</li>
<li><a
href="https://github.com/evanw/esbuild/commit/6e75bc74f17d09cbcf680b1902a0d4ad7757102c"><code>6e75bc7</code></a>
run <code>make update-compat-table</code></li>
<li><a
href="https://github.com/evanw/esbuild/commit/8f506d5ca6882f2fa96a4a7233ab9784af0a5298"><code>8f506d5</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/4292">#4292</a>:
support <code>with { type: bytes }</code></li>
<li><a
href="https://github.com/evanw/esbuild/commit/d6b668f96fb00d6a6d035f058e38b6bd2507beb6"><code>d6b668f</code></a>
publish 0.25.10 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/5088c198b5ecee18ba903c4099458df98b1b6788"><code>5088c19</code></a>
refactor: use strings.Builder (<a
href="https://redirect.github.com/evanw/esbuild/issues/4290">#4290</a>)</li>
<li><a
href="https://github.com/evanw/esbuild/commit/755da31752d759f1ea70b8d4f7f677b3557dab3e"><code>755da31</code></a>
run <code>make update-compat-table</code></li>
<li>Additional commits viewable in <a
href="https://github.com/evanw/esbuild/compare/v0.25.8...v0.25.11">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.25.8&new-version=0.25.11)](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>

Author: dependabot[bot]