tests: update output for compile-fail tests

Some of the error messages have changed in nightly Rust, since the
.stderr files were last checked.  Update everything.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Author: bonzini

tests/ui/compile-fail/init/missing_comma.stderr

@@ -1,4 +1,4 @@
-error: no rules expected the token `c`
+error: no rules expected `c`
   --> tests/ui/compile-fail/init/missing_comma.rs:16:9
    |
 16 |         c: Bar,
@@ -10,7 +10,7 @@ note: while trying to match `,`
    |         @munch_fields($field:ident $(: $val:expr)?, $($rest:tt)*),
    |                                                   ^
 
-error: no rules expected the token `c`
+error: no rules expected `c`
   --> tests/ui/compile-fail/init/missing_comma.rs:16:9
    |
 16 |         c: Bar,

tests/ui/compile-fail/init/missing_comma_with_zeroable.stderr

@@ -1,20 +1,14 @@
-error[E0782]: trait objects must include the `dyn` keyword
+error[E0782]: expected a type, found a trait
   --> tests/ui/compile-fail/init/missing_comma_with_zeroable.rs:12:15
    |
 12 |         a: 0..Zeroable::zeroed()
    |               ^^^^^^^^
    |
-help: add `dyn` keyword before this trait
+help: you can add the `dyn` keyword if you want a trait object
    |
 12 |         a: 0..<dyn Zeroable>::zeroed()
    |               ++++         +
 
-error[E0599]: no function or associated item named `zeroed` found for trait `pinned_init::Zeroable`
-  --> tests/ui/compile-fail/init/missing_comma_with_zeroable.rs:12:25
-   |
-12 |         a: 0..Zeroable::zeroed()
-   |                         ^^^^^^ function or associated item not found in `Zeroable`
-
 error[E0308]: mismatched types
   --> tests/ui/compile-fail/init/missing_comma_with_zeroable.rs:11:13
    |

tests/ui/compile-fail/init/no_error_coercion.stderr

@@ -5,7 +5,7 @@ error[E0277]: `?` couldn't convert the error to `std::alloc::AllocError`
 17 | |             a: Box::new(42),
 18 | |             bar <- init!(Bar { b: 42 }),
 19 | |         }? AllocError)
-   | |______________________^ the trait `From<Infallible>` is not implemented for `std::alloc::AllocError`, which is required by `Result<Foo::new::__InitOk, std::alloc::AllocError>: FromResidual<Result<Infallible, Infallible>>`
+   | |______________________^ the trait `From<Infallible>` is not implemented for `std::alloc::AllocError`
    |
    = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
    = help: the trait `FromResidual<Result<Infallible, E>>` is implemented for `Result<T, F>`

tests/ui/compile-fail/init/wrong_generics.stderr

@@ -1,4 +1,4 @@
-error: no rules expected the token `<`
+error: no rules expected `<`
  --> tests/ui/compile-fail/init/wrong_generics.rs:7:22
   |
 7 |     let _ = init!(Foo<()> {

tests/ui/compile-fail/pin_data/missing_pin.stderr

@@ -7,7 +7,8 @@ error[E0277]: the trait bound `impl PinInit<usize>: Init<usize, _>` is not satis
 13 | |         })
    | |__________^ the trait `Init<usize, _>` is not implemented for `impl PinInit<usize>`
    |
-   = help: the trait `Init<impl PinInit<usize>, _>` is implemented for `impl PinInit<usize>`
+   = help: the trait `Init<usize, _>` is not implemented for `impl PinInit<usize>`
+           but trait `Init<impl PinInit<usize>, _>` is implemented for it
    = help: for that trait implementation, expected `impl PinInit<usize>`, found `usize`
 note: required by a bound in `__ThePinData::a`
   --> tests/ui/compile-fail/pin_data/missing_pin.rs:4:1

tests/ui/compile-fail/pin_data/unexpected_item.stderr

@@ -1,10 +1,10 @@
-error: no rules expected the token `fn`
+error: no rules expected keyword `fn`
  --> tests/ui/compile-fail/pin_data/unexpected_item.rs:4:1
   |
 4 | fn foo() {}
   | ^^ no rules expected this token in macro call
   |
-note: while trying to match `struct`
+note: while trying to match keyword `struct`
  --> src/macros.rs
   |
   |             $vis:vis struct $name:ident

tests/ui/compile-fail/pinned_drop/no_fn.stderr

@@ -1,10 +1,10 @@
-error: no rules expected the token `)`
+error: no rules expected `)`
  --> tests/ui/compile-fail/pinned_drop/no_fn.rs:6:1
   |
 6 | #[pinned_drop]
   | ^^^^^^^^^^^^^^ no rules expected this token in macro call
   |
-note: while trying to match `fn`
+note: while trying to match keyword `fn`
  --> src/macros.rs
   |
   |             fn drop($($sig:tt)*) {

tests/ui/compile-fail/pinned_drop/unexpected_additional_item.stderr

@@ -1,4 +1,4 @@
-error: no rules expected the token `const`
+error: no rules expected keyword `const`
   --> tests/ui/compile-fail/pinned_drop/unexpected_additional_item.rs:10:5
    |
 10 |     const BAZ: usize = 0;

tests/ui/compile-fail/pinned_drop/unexpected_item.stderr

@@ -1,10 +1,10 @@
-error: no rules expected the token `const`
+error: no rules expected keyword `const`
  --> tests/ui/compile-fail/pinned_drop/unexpected_item.rs:8:5
   |
 8 |     const BAZ: usize = 0;
   |     ^^^^^ no rules expected this token in macro call
   |
-note: while trying to match `fn`
+note: while trying to match keyword `fn`
  --> src/macros.rs
   |
   |             fn drop($($sig:tt)*) {

tests/ui/compile-fail/zeroable/with_comma.stderr

@@ -1,4 +1,4 @@
-error: no rules expected the token `,`
+error: no rules expected `,`
   --> tests/ui/compile-fail/zeroable/with_comma.rs:11:13
    |
 11 |       let _ = init!(Foo {
@@ -15,7 +15,7 @@ note: while trying to match `)`
    |                                                     ^
    = note: this error originates in the macro `$crate::__init_internal` which comes from the expansion of the macro `init` (in Nightly builds, run with -Z macro-backtrace for more info)
 
-error: no rules expected the token `,`
+error: no rules expected `,`
   --> tests/ui/compile-fail/zeroable/with_comma.rs:11:13
    |
 11 |       let _ = init!(Foo {