[security solution] resolver_generator script uses transport.request without a leading /

[pmuellr]

I recently had to fix some usages of transport.request for alerting, where the paths we were using did not have a leading /. Turns out, that works fine locally, and in CI, but does not work in Cloud. You need to have the path start with a leading / (at least for most uses).

Did a quick search through the code base to see if there were any others, and found this one.

kibana/x-pack/plugins/security_solution/scripts/endpoint/resolver_generator.ts

Line 32 in 6f57fa0

await client.transport.request({ method: 'DELETE', path: `_data_stream/${index}` });

Since this seems to be a stand-alone script vs code used in Kibana, I'm guessing there is no actual problem here, but perhaps it should be changed should this code get moved into Kibana at some point.

[elasticmachine]

Pinging @elastic/siem (Team:SIEM)