This is a follow on issue#1771
We need to have allways same response when user exists/notExists

• PR fix issue 1770: #1773 resolves the case when email service is setup
• when email service is not setup the server should return Email service is not set up also when username do not exist
• when email service is setup, and email do not exist the server returns Account recovery email has not been provided
  these are/should be rare cases when email is setup and only on really experimental server.
  When username do not exist I propose to return the actual no error

Adding (in username if (!exists)) a call to verifyEmailDependencies ()

Also replacing throw error with success

with

if (userAccount && !userAccount.email) {
  return resetLinkMessage ()

fix branch created fix/issue#1774