We've now got an (optional) param in the z-cam backend that will skip the configuration ritual, mostly for the sake of testing (I don't really see much sense in mocking all of the endpoints we hit while configuring the camera).
This param doesn't have a matching env var; I don't think this is something that we'll actually use outside of for tests.

This was causing the test to fail, as nock expects the headers to be
given as an object instead of a string, which made nock send invalid
imagery data and the `removeOrientation` function failed due to it not
being an actual JPEG image.

Before all the params were dispatched into the background, and failures
would not be caught, this will wait until they have all completed and
were succesful.

Otherwise, this would print out a bunch of
`UnhandledPromiseRejectionWarning`s.

Also `_makeReq` -> `_setParam` as it was before.

This was the only configuration that actually worked on the camera.

The options that are commented out aren't strictly necessary and we ditched them in the interest of time. If we want to be thorough, someone should check that they work as expected with the camera.

Also, there's some subtle/undocumented behavior for some of the options:
  - sharpness can't actually be set (see: ' Normal ')
  - we set lcd to On, but then set the timeout so that:
    + the screen is off for the flight
    + but, humans can still turn the screen back on without needing to write `curl` commands
  - more in the comments