Telegram Connector: Parse edited messages as if new message

[FabioRosado]

Description

I have decided to just implement @iobreaker easiest solution to the edited_message issue. I have tested the connector with an edited message and as reported everything worked fine 👍

The test added was meant to keep coverage to 100% when I ran the test to see if opsdroid.parse was called it would always return False - maybe I have to call parse twice but I'm not entirely sure 🤔

Fixes #862

Status

READY | UNDER DEVELOPMENT | ON HOLD

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

• Tox - all green
• Ran opsdroid with the fix, edited message, opsdroid parsed newly edited message.

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation (if applicable)
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[codecov]

Codecov Report

Merging #866 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #866   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          34     34           
  Lines        2115   2117    +2     
=====================================
+ Hits         2115   2117    +2

Impacted Files	Coverage Δ
opsdroid/connector/telegram/__init__.py	100% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 285d6df...c4aa884. Read the comment docs.

[jacobtomlinson]

Nice stuff. I like the code to test ratio in this PR 😆.