The import module does not correctly hash R66 partner passwords

In R66, unlike other protocols, when a server authenticates itself, it sends a "special hash" of its password instead of the password itself. In effect, the "special hash" acts as a password.

As a result, unlike other passwords which are simply hashed using bcrypt, the passwords of R66 partners have to be hashed first using the special R66 hash algorithm, before being hashed again with bcrypt.

In version 0.8.0, with the changes to the import module, passwords are now hashed by the import module itself, before opening the import transaction. This was done to reduce the amount of time the database transaction is open. However, the import module is missing the R66 hash step for R66 partners. As a result, all R66 partners added using the import module are imported with an incorrect password, and thus cannot be used for any transfers (since the partner authentication always fails).