Add lint rule for #[deprecated] on re-exports

[kailan]

As reported in #30827 and #84584, marking a re-export (pub use) with #[deprecated] does not produce a warning for consumers. In fact, there are instances of this in the core and std crates (see past issue #82080 where this caused some confusion).

This change modifies the stability annotation visitor to mark #[deprecated] annotations on use statements with AnnotationKind::DeprecationProhibited so that library developers are aware that the annotation is not warning their users as expected.

#[deprecated]
pub use a_module::ActiveType;

error: this `#[deprecated]` annotation has no effect
  --> $DIR/deprecated_use.rs:6:1
   |
LL | #[deprecated]
   | ^^^^^^^^^^^^^ help: remove the unnecessary deprecation attribute
   |
   = note: `#[deny(useless_deprecated)]` on by default

error: aborting due to 1 previous error

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pnkfelix (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue