Refactor errors to wrap errors
What does this MR do?
Refactor errors to wrap errors
- Wrapping error adds context to errors and helps in debugging problems.
- This is a standard Go practice.
Why was this MR needed?
To provide better context when errors are logged.
What's the best way to test this MR?
go test ./network/...
What are the relevant issue numbers?
Not directly related, but error wrapping could help troubleshooting issues like these: gitlab#341293