Windows password database column bugfix

I had first set the `encrypted_password` column to `VARCHAR(255)`. When I realized this was too short, I changed it to `TEXT` but did so in the same migration file. This caused some installed environments to not make the update.

Reverted it in the old migration file and created a new migration file to change the column type. This will apply the change on current environments with a simple package update and will not cause any data loss.