Auto merge of #27831 - servo:dependabot/cargo/bytemuck-1.4.1, r=jdm

Bump bytemuck from 1.2.0 to 1.4.1

Bumps [bytemuck](https://github.com/Lokathor/bytemuck) from 1.2.0 to 1.4.1.
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/Lokathor/bytemuck/blob/main/changelog.md">bytemuck's changelog</a>.</em></p>
<blockquote>
<h2>1.4.1</h2>
<ul>
<li><a href="https://github.com/thomcc">thomcc</a> fixed up the CI and patched over a soundness hole in <code>offset_of!</code>.
<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/pull/38">PR 38</a></li>
</ul>
<h2>1.4</h2>
<ul>
<li><a href="https://github.com/icewind1991">icewind1991</a> has contributed the proc-macros
for deriving impls of <code>Pod</code>, <code>TransparentWrapper</code>, <code>Zeroable</code>!! Everyone has
been waiting for this one folks! It's a big deal. Just enable the <code>derive</code>
cargo feature and then you'll be able to derive the traits on your types. It
generates all the appropriate tests for you.</li>
<li>The <code>zeroable_maybe_uninit</code> feature now adds a <code>Zeroable</code> impl to the
<code>MaybeUninit</code> type. This is only behind a feature flag because <code>MaybeUninit</code>
didn't exist back in <code>1.34.0</code> (the minimum rust version of <code>bytemuck</code>).</li>
</ul>
<h2>1.3.1</h2>
<ul>
<li>The entire crate is now available under the <code>Apache-2.0 OR MIT</code> license as
well as the previous <code>Zlib</code> license
<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/pull/24">#24</a>.</li>
<li><a href="https://github.com/HeroicKatora">HeroicKatora</a> added the
<code>try_zeroed_slice_box</code> function
<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/pull/17">#10</a>. <code>zeroed_slice_box</code> is
also available.</li>
<li>The <code>offset_of!</code> macro now supports a 2-arg version. For types that impl
Default, it'll just make an instance using <code>default</code> and then call over to the
3-arg version.</li>
<li>The <code>PodCastError</code> type now supports <code>Hash</code> and <code>Display</code>. Also if you enable
the <code>extern_crate_std</code> feature then it will support <code>std::error::Error</code>.</li>
<li>We now provide a <code>TransparentWrapper&lt;T&gt;</code> impl for <code>core::num::Wrapper&lt;T&gt;</code>.</li>
<li>The error type of <code>try_from_bytes</code> and <code>try_from_bytes_mut</code> when the input
isn't aligned has been corrected from being <code>AlignmentMismatch</code> (intended for
allocation casting only) to <code>TargetAlignmentGreaterAndInputNotAligned</code>.</li>
</ul>
<h2>1.3.0</h2>
<ul>
<li>Had a bug because the CI was messed up! It wasn't soundness related, because
it prevented the crate from building entirely if the <code>extern_crate_alloc</code>
feature was used. Still, this is yanked, sorry.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/Lokathor/bytemuck/commit/68ed5fe6f21d1b0bbdb0b15abcb42e9a094c36ac"><code>68ed5fe</code></a> (cargo-release) version 1.4.1</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/64cc5973c451e92144f20e7a70e04e6de2ef6883"><code>64cc597</code></a> Add more tests, overhaul CI, and fix plug soundness hole in `bytemuck::offset...</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/343c618fea24089a8644b984d4e5ac2bc6917290"><code>343c618</code></a> Mark playground as all-features (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/37">#37</a>)</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/e013e747e78d284c1cf1c9e0bc5fbeda80312ed1"><code>e013e74</code></a> Add/rename LICENSE files (<a href="https://github-redirect.dependabot.com/Lokathor/bytemuck/issues/36">#36</a>)</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/b816a1b585dab6fb64df10920635a03ce3d6ff91"><code>b816a1b</code></a> (cargo-release) start next development iteration 1.4.1-alpha.0</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/426df7c9c068bd71938b13f09f0468c4541bd6f1"><code>426df7c</code></a> (cargo-release) version 1.4.0</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/6632bcef2cc6fdfb89034743da97ffa5d2b3cb3a"><code>6632bce</code></a> Update Cargo.toml</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/09ab956beae86ea0b1cf83cfbf3b1d24153d8ae6"><code>09ab956</code></a> update the optional derives to the released version</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/c171ac4f5bb5f0946683f68b329cd1caf65708c1"><code>c171ac4</code></a> (cargo-release) start next development iteration 1.0.1-alpha.0</li>
<li><a href="https://github.com/Lokathor/bytemuck/commit/9aedc156a8e27b99ade4cbe3bed9eae9a42ae864"><code>9aedc15</code></a> (cargo-release) version 1.0.0</li>
<li>Additional commits viewable in <a href="https://github.com/Lokathor/bytemuck/compare/v1.2.0...v1.4.1">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=bytemuck&package-manager=cargo&previous-version=1.2.0&new-version=1.4.1)](https://dependabot.com/compatibility-score/?dependency-name=bytemuck&package-manager=cargo&previous-version=1.2.0&new-version=1.4.1)

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)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)

</details>

0 files changed, 0 insertions, 0 deletions