1. Notify config has now become a domain resource, so that each domain can have its own configuration about notify.
The domains has no configuration will use system config.
2. Robot separates from config and becomes a shared project resource. Sending information to robot can
choose which robot to send to.
* feat(notify): Add 'get-types' action for ConfigManager
The List interface is only open to administrators,
because we don't want anyone other than administrators
to see the details of the notify configuration.
To let general user to kown available notification channels,
add 'get-types' actions of ConfigManager.
* feat(notify): Check the availability of contact type before creating notification
Creating notification with unconfigured contact type will fail at
sending message. Now, prevent creation in advance.
* feat(notify): Add workwx for NotifyNormal/Important/Critical
* feat(notify): Add Notify about robot in notifyclient
* fix(notify): Init ParentContactType for SSubContact
1. ParentContactType of SSubContact with webconsole type is empty.
2. ParentContactType of others SSubContact is mobile.
* fix(notify): Unverify SSubContact when ParentContactType match
* fix(notify): When no data is initialized, exit directly
* refactor(notify): ALL
* feat(climc): Notify v2
* feat: support notify for codegen.py
* delete deprecated code and Maintain SDK compatibility
* Adjust the template for mail validation to support captcha
* fix: The issue of notify refactoring
* add copyright for notifyv2 cli
* Adjust according to the advice of make check
* Remove utils package in notify
* fix import format
* remove redundant Template module
* fix validateCreate and validateUpdate of notifytemplate
* fix update issues of receivers
* fix: Add SetStageComplete in tasks
1. Uname is availbale now in api via adding "uname=true" in query.
So we can use uname in climc which is much more visual and use uid in
web client which avoid time-consuming remote calls that may occur.
2. Previously, the template for the message was managed by the
individual sending components. Now, these templats was managed uniformly
by Notify Service so that we can easily add and remove.
3. Now, failure to send a validation message will trigger a notification
to the user via websocket.
