Tracking issue for release notes of #143857: Port #[macro_export] to the new attribute parsing infrastructure

[rustbot]

This issue tracks the release notes text for #143857.

cc @Periodic1911, @oli-obk -- original issue/PR authors and assignees for drafting text

See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.

Release notes text

This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:

• Does this need an additional compat notes section?
• Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?

# Compatibility Notes
- As part of the larger effort refactoring compiler built-in attributes and their diagnostics, [The future-compatibility lint `invalid_macro_export_arguments` is upgraded to deny-by-default and will be reported in dependencies too.](https://github.com/rust-lang/rust/pull/143857)

Tip

Use the previous releases for inspiration on how to write the release notes text and which categories to pick.

Release blog section

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.

Over the past few releases, many changes were made to the way built-in attributes are processed in the compiler. This should greatly improve the error messages and warnings rust gives for built-in attributes and especially make these diagnostics more consistent among all of the over 100 built-in attributes. To give a small example, in this release specifically, rust became stricter in checking what arguments are allowed to `macro_export` by [upgrading that check to a "deny-by-default lint" that will be reported in dependencies.](https://github.com/rust-lang/rust/pull/143857). 

Note

If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.

[jdonszelmann]

This is effectively a bug fix in the internals of the compiler. The result is user-facing, because we didn't validate our input properly in the past and now we do. If we want to mention anything at all about this, it could be nice to put in a little text that attributes (in general) are being reworked in the compiler and some of the consequences of that. I'd be willing to write a little text about that :)

[cuviper]

@jdonszelmann I'm categorizing this as a compatibility note -- if you could write that as a blurb of what users should be aware of here, that would be great!

[jdonszelmann]

Yea!

[jieyouxu]

@jdonszelmann I changed the relnotes wording to sth like

The future-compatibility lint invalid_macro_export_arguments is upgraded to deny-by-default and will be reported in dependencies too.

Feel free to edit if there's a more accurate wording.

[jdonszelmann]

@jieyouxu what would you think about maybe adding "As part of the larger effort refactoring compiler built-in attributes and their diagnostics, ...". To give a little shoutout to some of the other similar things we've changed in the last couple of releases.

[jieyouxu]

Feel free to add more context, I only edited the previous relnotes since it doesn't say anything "interesting" from a user POV.