chore(deps): bump wasmtime-wasi from 39.0.1 to 41.0.4 in /demo/deps/wasmex/native/wasmex in the cargo group across 1 directory (#36)

Bumps the cargo group with 1 update in the
/demo/deps/wasmex/native/wasmex directory:
[wasmtime-wasi](https://github.com/bytecodealliance/wasmtime).

Updates `wasmtime-wasi` from 39.0.1 to 41.0.4
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/bytecodealliance/wasmtime/releases">wasmtime-wasi's
releases</a>.</em></p>
<blockquote>
<h2>v41.0.4</h2>
<h2>41.0.4</h2>
<p>Released 2026-02-24.</p>
<h3>Changed</h3>
<ul>
<li>Wasmtime's implementation of WASI now has the ability to limit
resource
consumption on behalf of the guest, such as host-allocated memory. This
means
that some behaviors previously allowed by Wasmtime can now disallowed,
such as
transferring excessive data from the guest to the host. Additionally
calls to
<code>wasi:random/random.get-random-bytes</code>, for example, can have
limits in place
to avoid allocating too much memory on the host. To preserve
backwards-compatible behavior these limits are NOT set by default.
Embedders
must opt-in to configuring these knobs as appropriate for their
embeddings.
For more information on this see the related security advisory with
further
details on knobs added and what behaviors can be restricted.
<a
href="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-852m-cvvp-9p4w">GHSA-852m-cvvp-9p4w</a></li>
</ul>
<h3>Fixed</h3>
<ul>
<li>
<p>Panics when adding too many headers to a
<code>wasi:http/types.fields</code> has been
resolved
<a
href="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-243v-98vx-264h">GHSA-243v-98vx-264h</a></p>
</li>
<li>
<p>Panic when dropping a <code>[Typed]Func::call_async</code> future.
<a
href="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xjhv-v822-pf94">GHSA-xjhv-v822-pf94</a></p>
</li>
</ul>
<h2>v41.0.3</h2>
<h2>41.0.3</h2>
<p>Released 2026-02-04.</p>
<h3>Fixed</h3>
<ul>
<li>Fix an incorrect mid-end optimization rule that could cause a
compiler panic
due to mismatched types.
<a
href="https://redirect.github.com/bytecodealliance/wasmtime/pull/12504">#12504</a></li>
</ul>
<h2>v41.0.2</h2>
<h2>41.0.2</h2>
<p>Released 2026-02-03.</p>
<h3>Fixed</h3>
<ul>
<li>Reduce the dependencies of the
<code>wasmtime-internal-jit-icache-coherence</code> crate.
<a
href="https://redirect.github.com/bytecodealliance/wasmtime/pull/12446">#12446</a></li>
</ul>
<h2>v41.0.1</h2>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/bytecodealliance/wasmtime/blob/v41.0.4/RELEASES.md">wasmtime-wasi's
changelog</a>.</em></p>
<blockquote>
<h2>41.0.4</h2>
<p>Released 2026-02-24.</p>
<h3>Changed</h3>
<ul>
<li>Wasmtime's implementation of WASI now has the ability to limit
resource
consumption on behalf of the guest, such as host-allocated memory. This
means
that some behaviors previously allowed by Wasmtime can now disallowed,
such as
transferring excessive data from the guest to the host. Additionally
calls to
<code>wasi:random/random.get-random-bytes</code>, for example, can have
limits in place
to avoid allocating too much memory on the host. To preserve
backwards-compatible behavior these limits are NOT set by default.
Embedders
must opt-in to configuring these knobs as appropriate for their
embeddings.
For more information on this see the related security advisory with
further
details on knobs added and what behaviors can be restricted.
<a
href="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-852m-cvvp-9p4w">GHSA-852m-cvvp-9p4w</a></li>
</ul>
<h3>Fixed</h3>
<ul>
<li>
<p>Panics when adding too many headers to a
<code>wasi:http/types.fields</code> has been
resolved
<a
href="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-243v-98vx-264h">GHSA-243v-98vx-264h</a></p>
</li>
<li>
<p>Panic when dropping a <code>[Typed]Func::call_async</code> future.
<a
href="https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xjhv-v822-pf94">GHSA-xjhv-v822-pf94</a></p>
</li>
</ul>
<hr />
<h2>41.0.3</h2>
<p>Released 2026-02-04.</p>
<h3>Fixed</h3>
<ul>
<li>Fix an incorrect mid-end optimization rule that could cause a
compiler panic
due to mismatched types.
<a
href="https://redirect.github.com/bytecodealliance/wasmtime/pull/12504">#12504</a></li>
</ul>
<hr />
<h2>41.0.2</h2>
<p>Released 2026-02-03.</p>
<h3>Fixed</h3>
<ul>
<li>Reduce the dependencies of the
<code>wasmtime-internal-jit-icache-coherence</code> crate.
<a
href="https://redirect.github.com/bytecodealliance/wasmtime/pull/12446">#12446</a></li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/d938a9df47c8e62014c1a12571547411ede6ff5e"><code>d938a9d</code></a>
Release Wasmtime 41.0.4 (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12654">#12654</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/d86b00736b9ece60b3c81e52f7a7e4cdd9f7d895"><code>d86b007</code></a>
[41.0.x] Backport fixes for security advisories (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12650">#12650</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/db1c043b526578fb55633debe17d558b2c07c47d"><code>db1c043</code></a>
Release Wasmtime 41.0.3 (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12529">#12529</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/604f64b700afa0a23f553d254b83d415c5571d55"><code>604f64b</code></a>
[41.0] Backport Cranelift: mid-end: fix constant types in some
icmp/select ru...</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/881e9a384c38afece75ea1d616ce014ba11a24a7"><code>881e9a3</code></a>
Release Wasmtime 41.0.2 (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12499">#12499</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/1f6bc69de3a2597d91423e6ef846f6d8f470cac6"><code>1f6bc69</code></a>
Revert &quot;Release Wasmtime 41.0.2 (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12487">#12487</a>)&quot;
(<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12494">#12494</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/3a658147cc2e64c3ce9c64faabcd340fd899ff8a"><code>3a65814</code></a>
Switch back to emulation of s390x tests (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12492">#12492</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/67e082f868a97d9e4e20f01bce13658b2392b371"><code>67e082f</code></a>
Release Wasmtime 41.0.2 (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12487">#12487</a>)</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/2ca28e64a585b63f14ec6f1331f9a2c322002ac8"><code>2ca28e6</code></a>
Directly use anyhow rather than wasmtime-environ in
wasmtime-jit-icache-coher...</li>
<li><a
href="https://github.com/bytecodealliance/wasmtime/commit/c30fce86b19b422ff4059bdce136be45a49f1a1f"><code>c30fce8</code></a>
Release Wasmtime 41.0.1 (<a
href="https://redirect.github.com/bytecodealliance/wasmtime/issues/12434">#12434</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/bytecodealliance/wasmtime/compare/v39.0.1...v41.0.4">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=wasmtime-wasi&package-manager=cargo&previous-version=39.0.1&new-version=41.0.4)](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 show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/hyperpolymath/snifs/network/alerts).

</details>

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

Author: dependabot[bot]

demo/deps/wasmex/native/wasmex/Cargo.lock

@@ -20,7 +20,7 @@ rustler = { version = "0.37.2", features = ["big_integer", "serde"] }
 tokio = { version = "1.48", features = ["full"] }
 wasi-common = "39.0.1"
 wasmtime = "41.0.4"
-wasmtime-wasi = "39.0.1"
+wasmtime-wasi = "41.0.4"
 wasmtime-wasi-http = "39.0.1"
 wat = "1.243.0"
 wiggle = "39.0.1"