update ndt5 runner

[critzo]

Updates the ndt5 test runner to:

• Always use -protocol=ndt5 so all tests are in plaintext, or insecure websockets. This will eventually be replaced to support either protocol using an env var, but since most Murakami beacons we're testing on are either armv7 or arm64, removing the overhead of TLS is needed to support line rate measurement.
• Test runner supports using MURAKAMI_TESTS_NDT5_ENABLED=1 and MURAKAMI_TESTS_NDT5_HOST=<IP or FQDN> environment variables to define a specific, self-provisioned ndt-server to test to. Noting that this is an interim solution.

This update has been tested and confirmed working using a Balena managed Raspberry Pi 4.

[robertodauria]

A question: why not leaving the option to enable secure connections is the user wants to?

[critzo]

The issue is that Murakami is meant to run unattended, and the secure option is not suitable on the current recommended and tested hardware. I would like eventually to allow all of the binary's options to be configurable using the config file/env var methods we're using now, which I think should happen in the next re-write. So I'm definitely in favor of supporting it, but the current runner needs to only use non-TLS. In my tests, the measurements are at line rate for non-TLS, and perhaps at least 50% less when using TLS or wss.

[robertodauria]

LGTM if it's an interim solution, having the option to enable secure connections in future sounds nice but not needed and likely a bad idea for the current use cases.