[User Attribute Change Verification] The "Enable user mobile number verification on update" /"Enable user email verification on update" is getting triggered when "adding" a mobile number/email

[GoushiRam]

Describe the issue:
Scenario 1:
With the "Enable user mobile number verification on update" checked and the consumer user/admin tries to update the business user mobile number/email details
When adding a mobile number for an existing consumer user (not an update, but adding), the SMS cannot be triggered for the existing mobile, since the mobile number is blank. So this config should be exempted if the existing mobile number is blank/null.

Scenario 2:
Same behaviour is applicable if the email address is blank and "Enable user email verification on update" is checked

How to reproduce:

1. Check "Enable user email verification on update" under User Attribute Change configuration
2. Navigate to a consumer user with no mobile numbers
3. Add a mobile number and verify the behaviour

Expected behavior:
The mobile number should be allowed to add

Environment information (Please complete the following information; remove any unnecessary fields) :

• Product Version: [e.g., IS 5.10.0, IS 5.9.0]
• OS: [e.g., Windows, Linux, Mac]
• Database: [e.g., MySQL, H2]
• Userstore: [e.g., LDAP, JDBC]

---

Optional Fields

Related issues:

Suggested labels:

[UdeshAthukorala]

This will be fixed with:

• Update SMS provider payload template identity-apps#5573
• Update SMS provider payload template wso2-extensions/identity-event-handler-notification#220

[UdeshAthukorala]

This will be fixed with:

• Update SMS provider payload template identity-apps#5573
• Update SMS provider payload template wso2-extensions/identity-event-handler-notification#220

Reverted the above PRs due to a regresiion(#19750) and fixed this issue with wso2-extensions/identity-event-handler-notification#222