feature: upgrade to use udp unicast

[gilbert-sci]

Summary

In preparation for switching to UDP unicast, we have updated the StreamOut configuration to support udp unicast

Changes

• Updates synapse api
• Modularizes packet loss/bitrate calculation in streaming
• Updates stream out to use Udp unicast

Migration

StreamOut configurations can just be defined like this (with an empty configuration for stream_out)

    {
      "type": "kStreamOut",
      "id": 1,
      "stream_out": {
      }
    },

The client will automatically fill with the clients IP and a default streaming port. You can also set a different port yourself, like this:

    {
      "type": "kStreamOut",
      "id": 1,
      "stream_out": {
        "udp_unicast": {
          "destination_port": 12345
        }
      }
    },

Specific IP addresses will not work, unless it is your own. In most cases, just let the client figure out the correct IP/Port to use.

Testing

• Tested streaming from a device with the updated server
• Tested running the example on a device with an updated server
• Tested with starting/reading from synapse-sim
  • e.g. synapse-sim --rpc-port 50098

[polymerizedsage]

I have been doing some testing with this branch and the SciFi UDP unicast branch. A pain point I noticed is the inclusion of a destination IP in the config means that configs are not host-agnostic. If I change wireless networks or want to share the config to someone else, the destination IP needs to be updated. Perhaps the CLI can handle setting this field to the local IP address?

Ill wait till you are ready for review for any other comments.

[antoniaelsen]

I believe we don't need to bind to send, and we don't want to bind to the dest port if we want to receive on the same machine.

[antoniaelsen]

While you're here, technically this should be

Suggested change

	def read(self) -> Tuple[Optional[SynapseData], int]:
	def read(self) -> Tuple[Optional[Tuple[NDTPHeader, SynapseData]], int]:

(_unpack's signature is wrong as well)