The lint docs misrepresent trait `Drop`

The reason why Drop is a trait is because adding a drop method to a type is similar to implementing a trait on it.
Other than that, Drop does not really behave like a trait. If a type doesn’t implement Drop, then that doesn’t mean it lacks destructor code. For instance, String and HashMap currently don’t implement it.

Instead, core::mem::needs_drop::<T>() is used to check if dropping a T invokes a destructor.

drop_non_drop and forget_non_drop should ideally not mention the trait Drop in their name or documentation, it is misleading.

Start by locating the definitions and documentation for the drop_non_drop and forget_non_drop lints. Compare their wording with core::mem::needs_drop::<T>() and determine how the lint names and documentation should avoid implying that only types implementing Drop have destructor code; done means the misleading references are corrected.