[Ingest] Use agent template embeded in the pkg registry response

[nchaulet]

Summary

A few weeks ago @ruflin made a change to have agent stream template embedded in the response elastic/package-registry#335

We should use that instead of making an extra call to get the stream, also our code was not working for stream that were not named stream.yml (stream.yml.hbs)

[jen-huang]

Code LGTM, didn't test locally

[jfsiii]

Didn't run, but everything reads well.

Only comment is two small language issues. I believe the error messages should be "unable to find ..."

[ruflin]

There are two issues related to this:

• Some naming cleanup is needed: Adjust config options and naming for template.* package-registry#394
• Should this summary really be generated by the registry? Discuss: Where should the datasource summary happen? package-registry#348

Especially for the second one, I think there should be a summary somewhere but probably KB should take care of it when it downloads the package for the first time.

[nchaulet]

@ruflin Are you ok to merge it like this for alpha so we can support agent.yml.hbs template? and we can revisit how we build this for the beta. And yes kibana is probably the best candidate to build this resume.

[ruflin]

@nchaulet yes

[nchaulet]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 8c3c242

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