cryptsetup: rework how we log about activation failures
    
    First of all let's always log where the errors happen, and not in an
    upper stackframe, in all cases. Previously we'd do this somethis one way
    and sometimes another, which resulted in sometimes duplicate logging and
    sometimes none.
    
    When we cannot activate something due to bad password the kernel gives
    us EPERM. Let's uniformly return this EAGAIN, so tha the next password
    is tried. (previously this was done in most cases but not in all)
    
    When we get EPERM let's also explicitly indicate that this probably
    means the password is simply wrong.
    
    Fixes: #11498
    (cherry picked from commit 6f177c7dc092eb68762b4533d41b14244adb2a73)
    
    Related: #1776408
    
    patch_name: 0305-cryptsetup-rework-how-we-log-about-activation-failur.patch
    present_in_specfile: true
    location_in_specfile: 305
    squash_commits: true