Consider unpacking OTLP arrays

[cartermp]

From a customer request:

[...] ]does Honeycomb accepts array attributes on OpenTelemetry? Their documentation mentions that as a valid attribute type, but when I try to send an array of strings from our testing instrumentation library it seems like what I'm getting is a string representation of the array instead. I'm still investigating if this is happening on the Ruby SDK - the string below suggests this might be the case since the string value in there is exactly what Ruby would output if it generated the string representation of the array in question - but I would appreciate any insights there.

Like in #235, when we see an OTLP array we serialize the whole thing rather than add each element as an attribute.

Now, unlike key:value structures, arrays don't have named keys. So we'd have to consider naming each element based on an index. That might mean:

myArray: ["bananas", "kitty cats", "toilets"]

Would translate into:

{
  ...
  "myArray.0":"bananas",
  "myArray.1":"kitty cats",
  "myArray.2":"toilets",
}

[MikeGoldsmith]

We now track whether a customer is attempting to send array or bytes attributes.

See this shepherd ingest query