[SDK-2823] Fix password reset when using custom connection resolver

[stevehobbsdev]

Changes

This PR addresses an issue where, if using the password reset feature and also using a custom connection resolver, the email address is not auto-populated. This does happen if not using a custom resolver, so this PR aligns those scenarios.

It does this by copying the value from the username field into email, if the value validates as an email address (using non-strict validation).

Notes

• When using a custom resolver, usernameStyle is always username
• Password Reset always requires an email address. If the value doesn't validate as an email address (because you can enter either on the login screen) then the value is blanked out on the password reset screen.

References

Fixes #2038

Testing

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of the platform/language

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All code quality tools/guidelines have been run/followed
• All relevant assets have been compiled

[lbalmaceda]

@stevehobbsdev The changes in reset_password and its tests LGTM. I wonder if the rest of the diff was included by mistake, as those are mostly build files being removed --> +162 −48,564

Note that browserstack tests are failing

[stevehobbsdev]

I wonder if the rest of the diff was included by mistake

No, there is an explicit commit that removes them. I've discovered the downside of forcing ignored files into Git is that on the next commit they will be removed again, since Git will see them as deleted files. I think the least obtrusive way forward is to just include the build files in the repo and remove the entry from .gitignore.

Note that browserstack tests are failing

Yep, they will continue to intermittently fail until I invest some time in fixing them, which I am planning to do shortly.