Structured Logs: follow up - increase logs queue size

[JoshuaMoelans]

Currently we can queue up to 2 batches of 100 logs, but our specs have been updated with the following

SDKs MUST also have a hard limit of 1000 log events queued up to avoid causing your customers' applications going out of memory

We could extend our existing two-buffer-approach to a 10-buffer-ring, where on flush we 'walk' through all pending buffers (and we'd need to move our active-buffer-index update outside of the flush step), or we just increase the size of each queue

We should only do this if customers actually are missing logs, considering this is an upper bound limit to avoid applications going OOM.

[linear]

NATIVE-154

[JoshuaMoelans]

Closing for now, since the 1000 is an upper limit is to avoid going OOM, and in Native we (for now) seem to be fine with our 2x100-double-buffer approach. Can reopen if we ever get user reports of missing logs.