Lint on `black_box`ing ZSTs

If a function pointer is black boxed, the call is treated as opaque:

use core::hint::black_box;
use core::ops::Shl;

#[no_mangle]
pub fn coerce_to_fn() {
    let f: fn(u32, u32) -> u32 = u32::shl;
    let fbb = black_box(f);
    fbb(1, 2);
}

coerce_to_fn:
        push    rax
        lea     rax, [rip + <u32 as core::ops::bit::Shl>::shl::hf57c419aa60bbfeb]
        mov     qword ptr [rsp], rax
        mov     rax, rsp
        mov     edi, 1
        mov     esi, 2
        call    qword ptr [rsp]
        pop     rax
        ret

However, black boxing a ZST that implements Fn does nothing:

#[no_mangle]
pub fn with_zst() {
    let fbb = black_box(u32::shl);
    fbb(1, 2);
}

with_zst:
        ret

This difference is subtle and we should lint on it. Suggested by @beetrees.

For reference: https://rust.godbolt.org/z/nvoEcnxKh

Start by reproducing the two examples with black_box, comparing the function-pointer call with the ZST Fn call and inspecting the generated assembly. The issue does not name implementation files or tests; done means adding a lint that identifies this ineffective ZST black boxing and covering the behavior with an appropriate compiler test.