[Entity Analytics] Asset criticality bulk upload JSON API

[hop-dev]

Summary

Add the asset criticality bulk upload API at POST /api/asset_criticality/bulk. Records supplied will either be created or updated.

This API has the same functionality as the csv upload API but takes a JSON body.

A couple slight differences:

• only 1000 records can be supplied, I think this is a good number, I have capped this so we dont have to parse a huge body, I think if users want more than this in a single request they can use CSV which is better suited (parses request as data is received instead of parsing in one go)
• Validation is done up front not line by line, if an invalid record is received the whole request is aborted with a 400, no records are changed or added.

Example curl (note asset criticality advanced setting must be enabled otherwise you will get a 403):

> curl -X POST $KIBANA_URL/api/asset_criticality/bulk \
--header "kbn-xsrf: true" \
--header "Content-Type: application/json" \
--header "elastic-api-version: 2023-10-31" \
--data '{ "records": [ { "id_field": "host.name", "id_value": "host-1", "criticality_level": "low_impact" }, { "id_field": "host.name", "id_value": "host-2", "criticality_level": "high_impact" } ] }'

I have added API tests for the new route

[hop-dev]

/ci

[elasticmachine]

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

[tiansivive]

Just a small question

[szaffarano]

LGTM!

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: f0d79ac

Failed CI Steps

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
securitySolution	13.6MB	13.6MB	+226.0B

History

• 💔 Build #216704 failed b62c664
• 💔 Build #216182 failed 35f51d5

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @hop-dev