Issue #849. Catch decryption failure

[cintolas]

If decryption fails, catch the error and silently continue.
This prevents a misconfigured node from crashing nodes using Middlewares.Transport.Encryption

📝 Description

A misconfigured node should not crash other nodes.
I wrapped the decrypt code in a try/catch block. This will log the following error on the sender's side
[2020-12-28T22:09:47.008Z] WARN plaintext/TRANSPORTER: Invalid incoming GOSSIP_REQ packet

🎯 Relevant issues

#849

💎 Type of change

• [ x] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

📜 Example code

🚦 How Has This Been Tested?

Tested against the breaking code in case 849

🏁 Checklist:

• [x ] My code follows the style guidelines of this project
• [x ] I have performed a self-review of my own code
• 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
• I have commented my code, particularly in hard-to-understand areas

[coveralls]

Pull Request Test Coverage Report for Build 2590

• 4 of 4 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.0007%) to 92.062%

---

Totals
Change from base Build 2586:	0.0007%
Covered Lines:	7397
Relevant Lines:	7747

---

💛 - Coveralls

[icebob]

Nice job, but please don't use silent catch, because it makes the debugging difficult. Please add a logger.error because it's not a normal case and the developer should know about it.