Add WPush Notification Provider

[anhao]

⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

• I have read and understand the pull request rules.

Description

Add WPush Notification Provider

Type of change

Please delete any options that are not relevant.

• New feature (non-breaking change which adds functionality)

Checklist

• My code follows the style guidelines of this project
• I ran ESLint and other linters for modified files
• I have performed a self-review of my own code and tested it
• I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
• My changes generates no new warnings
• My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Event	Before	After
UP	-	paste-image-here
DOWN	-	paste-image-here
Certificate-expiry	-	paste-image-here
Testing	-	paste-image-here

[chakflying]

If this is an error condition, maybe we should do throw new Error(ret.data.message) instead.

[CommanderStorm]

Overall, this looks good.
I have left some inline comments below.

I have added a table to the PR-description. Could you fill it with the requisite screnshots?

Explanation on the second one:

Offering notifications is close to the core of what we are as an uptime monitor. Therefore, making sure that they work is also really important. Because testing notification providers is quite time intensive, we mostly offload this onto the person contributing a notification provider.

To make shure you have tested the notification provider, please include screenshots of the following events in the pull-request description:

• UP/DOWN
• Certificate Expiry via https://expired.badssl.com/
• Testing (the test button on the notification provider setup page)

[CommanderStorm]

I have not used said notification provider:
Is this option clear enough for the users?
Do they need an helptext on how to find this?

[anhao]

Think , Detailed channel descriptions can be viewed at the link below

[CommanderStorm]

Please refer to above review. I think you missed this paragraph:

I have added a table to the PR-description. Could you fill it with the requisite screnshots?

Explanation on the second one:

Offering notifications is close to the core of what we are as an uptime monitor. Therefore, making sure that they work is also really important. Because testing notification providers is quite time intensive, we mostly offload this onto the person contributing a notification provider.

To make shure you have tested the notification provider, please include screenshots of the following events in the pull-request description:

• UP/DOWN
• Certificate Expiry via https://expired.badssl.com/
• Testing (the test button on the notification provider setup page)