feat: add telegram/mattermost notif + auto relaunch

[ghost]

Describe the changes

• Add Telegram notification
• Add Mattermost notification
• Add Argparse with "delay" argument to allow ransomwatch to loop without cron (the default behavior is unchanged, but you can uncomment line in Dockerfile to let ransomwatch to loop every x seconds)

Related issue(s)

#42

How was it tested?

Tested with Telegram/Mattermost notification with fresh DB

[ghost]

Thank you @jychp, great job

[ghost]

I just add Mattermost notification

[captainGeech42]

Wow, this is awesome! Thanks for putting this together, I will review it ASAP and get this merged in!

Can you rebase to the HEAD commit on main?

[ghost]

Rebase done.

[danieleperera]

Tested telegram and delay features, both are working fine! 👍🏼
I'd suggest only some minor changes on config.yaml.
From telegram_apikey and telegram_chatid to just apikey and chatid.
These modifications should also be done in notification manager.

[ghost]

The better way to do this is to rework configuration:

dest1:
  type: slack
  slack:
    url: xxx
#  telegram:
#    apikey: xx
#    chatid: xx
#  other_tool:
#    key1: xx
dest2:
  type: telegram
#  slack:
#    url: xxx
  telegram:
    apikey: xx
    chatid: xx
#  other_tool:
#    key1: xx

This could allow to rewrite Manager in a more generic way:

MAPPING = {'telegram': TelegramNotification, ...}
if not MAPPING[params['type']].send_new_victim_notification(victim, params.get(params['type'], {}):
    logging.error(f"Failed to send new victim notification to {params['type']} \"{dest}\"")

[taycom]

Tested telegram and work perfect!

[captainGeech42]

Sorry for the delay on this, I have been busy moving and haven't been able to work on this.

Glad some other people have tested the Telegram stuff, that's great! Has anyone else tested the Mattermost one?