Dont stop peer connection on any exception

[asdacap]

Addresses #6014

• On one of the log @kamilchodola gave, the peer loop exited very early without any exception. mistake in task handling causes it to not wait for worker thread exit, but not a problem.
• There is a mistake in the tasks handling which hide the exception probably.
• This fixes it and make sure it does not stop trying on exception.
• Discovery thread does not seems to start after initial bootnodes connection.
• Seems like task scheduler from dotnetty, maybe hanging.
• Switching to explicitly running default task scheduler.

Changes

• Fix connection loop exception accidentally hidden.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

• Well, nothing bad happened for sure.

[asdacap]

Made a mistake with my personal log cleaner causing me to miss some important log. Everything seems to be working as expected except for not getting new nodes from bootnodes. @kamilchodola is verifying that #6035 fix the issue.

[asdacap]

Turns out #6035 does not fix the problem.