Tracking issue for release notes of #136490: Do not allow attributes on struct field rest patterns

[rustbot]

This issue tracks the release notes text for #136490.

Steps

• Proposed text is drafted by PR author (or team) making the noteworthy change.
• Issue is nominated for release team review of clarity for wider audience.
• Release team includes text in release notes/blog posts.

Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

# Compatibility Notes
- [Forbid attributes on `..` inside of struct patterns (`let Struct { #[attribute] .. }) =`](https://github.com/rust-lang/rust/pull/136490)

Tip

Use the previous releases categories to help choose which one(s) to use.
The category will be de-duplicated with all the other ones by the release team.

More than one section can be included if needed.

Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
Otherwise leave it empty.

cc @Skepfyr, @compiler-errors -- origin issue/PR authors and assignees for starting to draft text

[Skepfyr]

This does cause the compiler to reject code it previously accepted, however given crater found nothing and rustfmt deletes the offending code it's highly unlikely anyone will be affected by it, so I don't think much fuss needs to be made. I'd probably word the release not something like:

Reject attributes on .. inside struct patterns

It might be worth adding a few extra words to highlight that it was previously accepted? A code example would be nice but getting into pattern position is a lot of characters Struct { #[attr] .. } isn't the clearest and match foo { Struct { #[attr] ..} => () } } is long and might be misleading?