[feature] Desensitize sensitive information.

[ayu-v0]

What's changed?

#2792

This PR desensitizes the phone and email, while ensuring that the desensitized data cannot be submitted to the database.
The desensitization rule for a email is to replace it with a "." to make the email illegal and ensure that it cannot be submitted directly to the database.The same goes for cell phone numbers.

Here is a picture of the modification operation：

The following is the information of the database：

Checklist

• I have read the Contributing Guide
• I have written the necessary doc or comment.
• I have added the necessary unit tests and all cases have passed.

Add or update API

• I have added the necessary e2e tests and all cases have passed.

[tomsun28]

relate with #2800

[ayu-v0]

The merge error is caused by @Date and @description, I've fixed it @yuluo-yx

[tomsun28]

hi @ayu-v0 thanks for this pr.
I reviewed and found that this implementation is not very reasonable. In case user modify the old data, eg: receiver name, phone. Its impact will make people feel confused and think it is a bug.
and another case like send test alarm, it will use the serialize data [email protected] to send email and failed.
Suggest suspend this issue, investigate the desensitization methods of other platforms later.

[tomsun28]

Sorry for rejecting this PR you worked so hard on.

[ayu-v0]

Sorry for rejecting this PR you worked so hard on.

Thank you very much for your review. This PR may be because I considered that the desensitized data is the correct information that the user has verified, so I did not consider that the user might send the email with the desensitized information. Based on this scenario, I wonder if there are any solutions (if I can think of them, haha).