chore: Bump thiserror from 1.0.61 to 2.0.4

[dependabot]

Bumps thiserror from 1.0.61 to 2.0.4.

Release notes

Sourced from thiserror's releases.

2.0.4

• Eliminate needless_lifetimes clippy lint in generated From impls (#391, thanks @​matt-phylum)

2.0.3

• Support the same Path field being repeated in both Debug and Display representation in error message (#383)
• Improve error message when a format trait used in error message is not implemented by some field (#384)

2.0.2

• Fix hang on invalid input inside #[error(...)] attribute (#382)

2.0.1

• Support errors that contain a dynamically sized final field (#375)
• Improve inference of trait bounds for fields that are interpolated multiple times in an error message (#377)

2.0.0

Breaking changes

• Referencing keyword-named fields by a raw identifier like {r#type} inside a format string is no longer accepted; simply use the unraw name like {type} (#347)

  This aligns thiserror with the standard library's formatting macros, which gained support for implicit argument capture later than the release of this feature in thiserror 1.x.

  #[derive(Error, Debug)]
  #[error("... {type} ...")]  // Before: {r#type}
  pub struct Error {
      pub r#type: Type,
  }

• Trait bounds are no longer inferred on fields whose value is shadowed by an explicit named argument in a format message (#345)

  // Before: impl<T: Octal> Display for Error<T>
  // After: impl<T> Display for Error<T>
  #[derive(Error, Debug)]
  #[error("{thing:o}", thing = "...")]
  pub struct Error<T> {
      thing: T,
  }

• Tuple structs and tuple variants can no longer use numerical {0} {1} access at the same time as supplying extra positional arguments for a format message, as this makes it ambiguous whether the number refers to a tuple field vs a different positional arg (#354)

  #[derive(Error, Debug)]
  #[error("ambiguous: {0} {}", $N)]
  //                  ^^^ Not allowed, use #[error("... {0} {n}", n = $N)]
  pub struct TupleError(i32);

... (truncated)

Commits

• 70a1261 Release 2.0.4
• 4fde284 Merge pull request #391 from matt-phylum/needless-lifetimes
• aa19b7c suppress needless_lifetimes lints from clippy 0.1.83
• ad2f20b Use ui test syntax that does not interfere with rustfmt
• 15fd26e Release 2.0.3
• 7046023 Simplify how has_bonus_display is accumulated
• 9cc1d0b Merge pull request #384 from dtolnay/nowrap
• 1d040f3 Use Var wrapper only for Pointer formatting
• 6a6132d Extend no-display ui test to cover another fmt trait
• a061beb Merge pull request #383 from dtolnay/both
• Additional commits viewable in compare view

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 commands and options

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)

[dependabot]

Superseded by #1546.