SASL Pidgin - Include note about nick in use for old versions.

Versions 2.14.8 and older have a issue where sasl fails if your nick is in use on another connection. Pidgin will blindly append a "1" at the end of the nick in the AUTHENTICATE line and this causes sasl to fail.

https://developer.pidgin.im/ticket/15451

Version 2.14.9 fixed this by allowing you to explicitly set your account name in the Advanced settings tab.

* Add an advanced account option to IRC accounts for explicitly setting the
SASL login name. (PIDGIN-15451) (RR 1388) (Belgin Știrbu)

Some flavours of *nix include outdated versions:

Ubuntu 18.04 LTS - 2.12.0 - EOL in Apr 2023
Ubuntu 20.04 LTS - 2.14.0 - EOL in Apr 2030

POP_OS 22.04 - 2.14.8

Debian bullseye - 2.14.1

Users will most likely be using outdated versions of Pidgin for a while.

Today (Nov, 27, 2022 GMT-5) a user ran into this issue.

User joined #libera via webchat while using their accountname as the nick. User was trying to connect with Pidgin 2.14.8 (POP_OS 22.04) and was getting "account@irc.libera.chat disabled Incorrect Password". User verified password was correct and multiple people tried to help. After about one hour the above issue was discovered. User was advised to change their nick on the webchat connection. User successfully connected via Pidgin after changing their webchat connection nick.

Suggested text:

Note: If your nick is being used by another connection you will get a "Incorrect Password" message. Please upgrade to 2.14.9 or newer and set your SASL login name in the Advanced tab.

Pidgin 2.14.10:

Start by locating the documentation page covering Pidgin SASL account setup and the Advanced tab. Add the suggested note about nick collisions, the incorrect-password message, and upgrading to 2.14.9 or newer, then verify that the guidance matches the documented settings.