Make libpwquality check less restrictive

Is your feature request related to a problem? Please describe. With an introduction of libpwquality, the password entered is checked against certain requirements; it is simply refused if checking is unsuccessful (there is no way to bypass it).

Describe the solution you'd like If the password check is unsuccessful, warn the user about, but still allow him to use desired "unsafe" password (if he knows what he is doing and really insist on it).

Describe alternatives you've considered I have built the latest snapshot without libpwquality (fortunately it is possible in a relatively simple way), but this means I have to use another release for all users on some system because just some passwords don't pass; provide the way an user can enforce "unsafe" password would be much better alternative by my opinion.

Additional context There are password systems which check the password quality, but provide the simple way some user can enforce an "unsafe" password (additional confirmation about knowing what is being done, to enter the "unsafe" password again to enforce or something like that...). Why not provide something like that in TigerVNC as well?