WIP: added apiserver and api client implementation of change password.

Added the api server and client set password command

Added the change-password user command

Thing to consider: 
> SetPassword only lets you change the password of the currently logged in user. Should the api really force this or should the commands force this behaviour (but not allowing the user to be specified)

> The change-password command writes the new password back to the yaml. Maybe the new file should be output as well?
Should we support a mode of operation where if no password is given the client prompts the user for a password? It seems bad to encourage a process which leaves passwords in command line history.