Support wrapped templates produced by elastic-package dump

[cavokz]

This allows to use integration assets dumped by elastic-package as-is, which enclose an outer meta data layer otherwise rejected when sent to Elastisearch.

[DJRickyB]

Thank you for this. Please add a description to the issue (we are doing this because elastic-package dump produces wrapped objects, I think that's fine to mention here), and some documentation to the track reference docs

[DJRickyB]

This LGTM with one nit. I don't think we should work to support a leading . in the template-path (for the root element), but I think one is implied by the wording JSON path in the docs/docstrings. I know this was my wording, but if you agree I think it's better documented as the JSON field inside the file content that contains the template. That way, we support the dot-notation in the way that you've coded but there's no reason for anyone to plug a leading .

With just a docs change to this effect, I don't see a need for further review, but please feel free to re-request

[cavokz]

Yes, I also noticed this and you're right, better save some time now that we still remember this caveat. Fixed with d9ccf60.

[DJRickyB]

@elasticmachine run tests

[DJRickyB]

@elasticmachine update branch