add support Tencent SMS

[liuxingjun]

Description

Checklist

• I have reviewed the contributing guidelines.
• I have included unit tests for my changes or additions.
• I have successfully run make test-docker with my changes.
• I have manually tested all relevant modes of the change in this PR.
• I have updated the documentation.
• I have updated the changelog.

Questions or Comments

[nsano-rururu]

Would you like to add the following settings to schema.yaml?
https://github.com/jertel/elastalert2/blob/master/elastalert/schema.yaml

  ### Tencent SMS
  tencent_sms_secret_id: {type: string}
  tencent_sms_secret_key: {type: string}
  tencent_sms_sdk_appid: {type: string}
  tencent_sms_to_number: {type: array, items: {type: string}}
  tencent_sms_sign_name: {type: string}
  tencent_sms_region: {type: string}
  tencent_sms_template_id: {type: string}
  tencent_sms_template_parm: {type: array, items: {type: string}}

Add Tencent SMS between Telegram and The Hive.

https://github.com/jertel/elastalert2/blob/master/docs/source/elastalert.rst#overview

[nsano-rururu]

Added support for [Tencent SMS](https://intl.cloud.tencent.com/document/product/382/40606) - @liuxingjun

　　　　　　　　　↓

Added support for Tencent SMS - [#470](https://github.com/jertel/elastalert2/pull/470) - @liuxingjun

[liuxingjun]

@nsano-rururu I have finished editing

[nsano-rururu]

There are not enough test cases. Coverage is not 100%.

87% 121-124, 127

[nsano-rururu]

@liuxingjun

Is it difficult to implement the rest of the tests?

[liuxingjun]

@nsano-rururu The correct tencent_sms_secret_id is required to achieve 100% coverage

[nsano-rururu]

@jertel

100% coverage seems difficult, but some testing has been implemented. I think it's okay to merge, but are there any other points of concern?

[jertel]

100% coverage is attainable with mocks but then you're merely testing that the implementation can handle a (potentially flawed) mock response, which is of limited value.

So yes, I think it's good to approve and merge. @nsano-rururu Since you've been the primary reviewer I'll let you do that. Thank you.

Thank you for the contribution @liuxingjun.

[liuxingjun]

@nsano-rururu How soon can I use the helm version

[liuxingjun]

@jertel This is my first time using python, this is my first time to participate in open source, I can try to improve test coverage later

[jertel]

@liuxingjun That is fine. It would be a good exercise for you to learn how to use Python mocks. There are several examples in the existing alerter unit tests.

You can use the existing Helm release for 2.2.1 and change the image.tag param to latest to use your new Tencent SMS changes now. A new 2.2.2 release will likely be created within the next week or so.