chore: go waku connection issues

[fbarbu15]

PR Details

• Added StepsCommon where functionality that applies to all tests/steps should be added
• Refactored add peer to be more resilient and also work on go-waku. This seems to fix all random failures we seen between nim->go

Issues reported:

[romanzac]

LGTM. Common for steps might come handy as each functionality to test have its own nuances. It is not always possible to share code across all of them.

[fbarbu15]

LGTM. Common for steps might come handy as each functionality to test have its own nuances. It is not always possible to share code across all of them.

Yes, I used this kind of structure in the past with specific steps and then common ones and it scales well if you make sure you don't change the common code too often(if you change it often you will break stuff where you don't expect)
So we need to put in common steps code that will remain the same.