Users API defects

[morehappiness]

1. For all APIs, it uses checkPermission to check permission. We should make sure it considers the allowedScope when it's machine and follow the permission-checking logic in v3 java code.
2. For DELETE :userId/SSOUserLogin, should not pass ssoUserId parameter and should follow the exist logic in v3 java as https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/resource/UserResource.java#L300;
3. For findUsers method, the logic should be same as v3 java code. Currently, the logic is deviated from v3 java code a lot.
4. For registerUser method, validate logic is not right, such as validate password is not performed, validate handle, email logic is not consistent with java code; make sure the logic is consistent with v3 java code.

[morehappiness]

5. For POST :resourceId/profiles, we should validate the profile, call setAccessToken and addSocialProfile as we do in v3 java code.
   please follow https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/resource/UserResource.java#L662
6. we do not need social_login_provider in user related APIs as there is a defined ProviderTypes as v3 java code; should update related logics.

[morehappiness]

7. PATCH resetPassword, POST resendEmail are not available;
8. for POST resendActivationEmail, should follow the logic begins from https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/resource/UserResource.java#L1065
9. for PUT activate, the logic begins from https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/resource/UserResource.java#L1119 are not implemented correctly
10. for PATCH :resourceId/email, when calling userService.updatePrimaryEmail, why does the code generate otp and send the email while not do that in v3 java code?
11. for PATCH :resourceId/status, should add comment query parameter to createUserAchievement and should activateEmail(see https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/dao/UserDAO.java#L767) and call publishNotificationEvent as we do in v3 java.
    11.1. in userService.updateStatus, when setting welcomeTemplateId, we should consider regSource as we do in v3 java code sendWelcomeEmailEvent method, see https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/resource/UserResource.java#L2483.
12. for get resetToken, should follow getResetPasswordUrlPrefix method in v3 java to get the resetPasswordUrlPrefix, see https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/resource/UserResource.java#L2158.
13. in validationService.validateHandle, should call isInvalidHandle and isHandleContainingNGWord as in v3 java, see https://github.com/appirio-tech/identity-service/blob/bf2428ea6997e115b317eb419c5e2c1c6029cdf5/src/main/java/com/appirio/tech/core/service/identity/dao/UserDAO.java#L959;
14. for :resourceId/2fa, twoFactorAuthService#updateUser2faStatus, remove diceEnabled related logic; just make sure mfaEnabled logic is cosistent with v3 java code;
15. for POST sendOtp, POST resendOtpEmail, POST checkOtp, we should use user_otp_email table instead of cache for otp and v3 java logic should be followed exactly;
    15.1. why delete the otp cache and check user exists or not again in twoFactorAuthService.resendOtpEmailFor2fa and checkOtpAndCompleteLogin?
16. For all the APIs with selector parameter, we should consider selecting specified fields only.
    getCacheKeyForOneTimeToken