Notification Plugin Initialization Failures Should Be More Verbose

[caronc]

💡 The Idea
With respect to a very good point brought forth in #460, Apprise isn't very verbose in the late stages of parsing a URL it supports. For example, if you pass in invalid://just-a-bad-apprise-query-in-general: you get an expected error that the URL could not be parsed.

However, if you successfully process a very valid URL that makes it all they way to the __init__() call of the very plugin in charge and it fails there (with a TypeError exception internally), the logging reason is only a WARNING.

A new standard needs to be in place where this changes to a ERROR type (for __init__ only) granting more information to the user calling an almost valid Apprise URL why it failed to be parsed.

Another consideration is privacy; logging information (with the exception of DEBUG) should not write anything into the logs that is privacy related. Error's that involve tokens or passwords in the __init__() should not write these tokens/passwords to the logs.

🔨 Breaking Feature
nothing will break.