Separate Notify from NotifyPayload, support for mqtt text type, other Notification fixes

[infeeeee]

Separated payload based notify from classic notify. The reason: there is a new mqtt entity supported by HomeAssistant: MQTT Text: https://www.home-assistant.io/integrations/text.mqtt/

With this changes you can send custom notification directly from home assistant webui!

The format accepted: Title|Message. If there is no | character it will display everything as the title.

Also with this changes the config check working again for classic notify, it gives a warning if no predefined title and message found.

[infeeeee]

Changed Windows notification module to tinyWinToast

Reasons:

• Win10toast was giving me strange warnings
• With this module it's possible to change the name of the sending app, on win10toast it showed Python, now it's IoTuring
• Win10toast only supports icons in .ico format, this supports pngs

For the icon, I just downloaded an official home-asssistant icon from here https://github.com/home-assistant/assets/blob/master/logo/logo-small.png

If IoTuring would have a logo, I would replace it.

[infeeeee]

Also removed notif2 dependency, as it is also deprecated: https://notify2.readthedocs.io/en/latest/#notify2-api-documentation

This package required most of the other linux prerequisites, so it makes installation much more streamlined.

notify-send is installed with libnotify, used by all des, so if someone uses a gui on linux, it should be installed. On a terminal only install than it will fail on PostInitialize()

[richibrics]

Hi, I liked so much your edits to work with HomeAssistant new Text component.
However I thought that separation of the Notify entity would have caused some confusion so I think this is the best solution: if configuring it, title and message are provided, those will be used; otherwise the Text component of HASS will be displayed (it becomes a NotifyPayload).

[infeeeee]

I think you can pull this, I don't want to add anything else 🚀