Fixes

[lhannest]

• Increased read timeout (now read timeout is set along with connection timeout). Sometimes beacons were returning in a reasonable amount of time, but a timeout error was still being thrown because the response was too big to read in the default amount of time. This doesn't appear to be happening anymore.

• Added discovered and processed counts to the concept and statement status endpoints. The discovered count is set the moment the beacon responds.

• Now processing (building cliques and saving to the database) beacon responses in batches. The processed count will go up by the batch size each time a batch is completed, which is set to 10 by default.

• I ended up keeping the original count because it's useful for cases when the status is 201.

Example of output:

{
   "queryId":"ZAxp8UHR7vd5hwVvSB0k",
   "status":[
      {
         "beacon":1,
         "status":200,
         "discovered":0,
         "processed":null,
         "count":0
      },
      {
         "beacon":2,
         "status":102,
         "discovered":61,
         "processed":null,
         "count":null
      },
      {
         "beacon":3,
         "status":102,
         "discovered":160,
         "processed":60,
         "count":null
      },
      {
         "beacon":4,
         "status":200,
         "discovered":24,
         "processed":24,
         "count":24
      }
   ]
}