improve error logging for JS/TS ping test

[GlenDC]

helps debugging issues in case
things go haywire while testing the JS implementation

[MarcoPolo]

Thanks. What errors did you run into that this logged?

If you have time, could you rebase to #121. If not, no worries. I can take :)

[GlenDC]

Thanks. What errors did you run into that this logged?

If you have time, could you rebase to #121. If not, no worries. I can take :)

Rebased it.

Two issues:

1. fetch API that wasn't defined, which was a redis-proxy error that was previously silenced. Fix was to use node v18, but hard to know if I do not see the error
2. second error was related to something going wrong in the Ping call, cannot remember exactly anymore what. Know it was an issue on my end as well. But that thing now just returns an AggregateError, which when logged just says that All promises got rejected. So not useful. Logging the errors itself does reveal it.

[thomaseizinger]

I am no JS expert but I think if you pass the err as an argument to console.error, it will display a nice stacktrace.

Suggested change

	console.error(`unexpected exception in ping test: ${err}\n Errors: ${err.errors}`)
	} else {
	console.error(`unexpected exception in ping test: ${err}`)
	}
	console.error(`unexpected exception in ping test: ${err}\n Errors: ${err.errors}`)
	} else {
	console.error(`unexpected exception in ping test`, err)
	}

[GlenDC]

Could be. Feel free to take over this PR by the way @MarcoPolo. You probably know better what you want to do with this suggestion and PR. My intention was more to share the need for better error logging in case the happy path is not being followed.

[ddimaria]

@GlenDC this PR has merge conflicts

[MarcoPolo]

I'm taking this pr.

[MarcoPolo]

Added logs to #121