Create judging_run_output together with judging_run

[eldering]

This means that the data state is more consistent.

Also, before the fix bb5d4c8, the judgedaemon
would retry the API call leading here after a 500 response
and then try to recreate the judging_run_output row of the
associated judging_run, which was already created in the first
API call, leading to an error

[Nov 23 14:47:57.923] judgedaemon[813572]: warning: Error while executing curl POST to url http://localhost/domjudge/api/judgehosts/add-judging-run/tiger-1/2589899: http status code: 500, request size = 5400, response: array (
  'code' => 500,
  'message' => 'An exception occurred while executing a query: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry \'2575471\' for key \'PRIMARY\'',