Merge users and admins

This means:

• add another column in the database for each user specifying the algorithm used to hashing (or empty for clear text). Example: MD5, SHA512, SHA256
• based on the above field, the password field will be either the clear text password or the hashed password
• in the CWS, at login, compare the passwords based on the algorithm specified in the database
• don't show passwords for users that use a hash function in the AWS but display a message showing the algorithm used. the admin can still change the password
• add option to specify hash in cmsAddUser

Pros:

• different types of users (users for a local contest with clear text password and users for remote contests in the same database)
• in the future, this will work well with an option for users to change their password only if allowed by the admins
• better security overall
• users can use password that are easier to remember for them and I can guarantee my users that I can't see their passwords

Cons:

• additional column in the database - bigger database
• with password hash, the admins can't recover a password, only change it

Start by mapping the database schema and the CWS login, AWS user display, and cmsAddUser entry points named in the issue. Define how clear-text and hashed passwords are represented, compared, displayed, and changed, including migration and security implications. Done means the merged user/admin flow supports the requested hash selection without exposing hashed passwords.