test(fix): Fix sporadic whatsapp service test fails

[nikoksr]

Description

Increase the connectivity timeouts for the WhatsApp service and change the order of execution for some assertments in the testfile.

Motivation and Context

We're currently experiencing a bug in our CI where the whatsapp.New method fails inconsistently. The bug is not reproducible on a local machine, so I'm guessing here that too short timeouts may be the issue.

How Has This Been Tested?

Difficult to test since bug only occurs in GitHub's CI. I was so far not successful in reproducing it locally.

Types of changes

• 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 change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[nikoksr]

@svaloumas the Whatsapp service's test fails sporadically in CI, which is very annoying, since we have to keep re-running the failed CI job until it succeeds. It's most likely a false positive and I can't reproduce it locally, so I'm taking a "blind" guess here.

The timeouts may fix the bug itself but also the assert order may be beneficial, since asserting a nil-error first, would reveal to us the actual underlying error in case of a failed test.

Edit: Aaaand it failed immediatly. But, it did report the underlying error, which is: couldn't dial whatsapp web websocket: websocket: bad handshake. Looks like the better solution to just tackle #274 instead of keeping an already dead service "alive".