The display details are not yet implemented, but those will be fleshed
out in the ThreatMatchRow component.

This data is not used by any existing row renderers and so this commit
is mostly just plumbing that data through.

This is necessary, however, for our new threat match row renderer as it
requires nested fields, which cannot be retrieved through the mechanism
that retrieves the existing row renderer data. However, these nested
fields are available, if requested, through this other data structure,
hence this plumbing.

For now to minimize changes I'm marking this as an optional field;
however in reality a value will always be present.

Updates logic, tests and mocks accordingly.

* helpers
* explicit fields file, which will hopefully be part of the renderer API
  at some point
* parent component to split data into "rows" as defined by our renderer
* row component for stateless presentation of a single match

Adds tentative copy, example row, and accompanying mock data.

…ed fields being flattened

I haven't yet deleted the old (new?) unused path yet. Cleanup to come.

* Rewrites isInstance logic for new data as helper, hasThreatMatchValue
* Updating types and tests
  * Adds to the previously empty ThreatEcs

This reverts commit 19c93ee.

We ended up extending the existing data (albeit from the fields
response!).

* adds contextId and eventId to pass to draggable
* We don't have a order-independent key for each individual
  ThreatMatchRow, due to matched.id not being mapped/returned in the
  fields response
* Fixes up a few things related to using the new data format

* Adds missing Threat ECS types

In order to use these in both the row renderer and the server request,
we need to move them to common/

These are currently hardcoded on the backend of the events/all query
(via TIMELINE_EVENTS_FIELDS); declaring them on both ends is arguably
confusing, and we're going with YAGNI for now.

This was causing type errors as this enum exists both here and in
common/, and I had only updated one of them.

One is still failing due to an outdated test subject, but I expect this
to change after an upcoming meeting so leaving it for now.

One for displaying match details, and another for indicator details

The indicator details will be sparse, so there's going to be some
conditional rendering in there.

* Adds translations for copy
* Fixes most of our layout woes with more flexbox!
* Conditional rendering of indicator details based on data
* tests

Leverages the existing FormattedFieldValue component, with one minor
tweak to add this field to the URL allowlist.

The draggable badges are a little odd in that their full box isn't
indicated until hover, making the visual weight a little off.

…erer

These tests are all implicitly testing the list of row renderers.

At certain container widths, a half-width hr is not sufficient.

Obviates the need for the accompanying comments.

Also ensures less traffic to urlhaus ;)

Gennin' beanz

We need to add the row index to our contextId to ensure that our
draggables work correctly for multiple rows, since each row will
necessarily have the same eventId and timelineId.