Add validation for template_path at input packages

[teresaromero]

What does this PR do?

• Adds validation rule for input type packages regarding the template_path at the policy_template
• Changes the input spec to have the field template_path required

Why is it important?

When an input package does not define its template_path at the policy_templates objects, fleet throws an error
here

This is caused because, the stream created from the input here has an undefined template_path. For inputs, there is no default value.

When a value is defined at template_path, fleet looks for the asset taking into account it ends with the given value here so it might be under the agents/input folder, or any other as long as it ends with the value.

Checklist

• Added unit tests for the validation rule

• I have added test packages to test/packages that prove my change is effective.

• I have added an entry in spec/changelog.yml.

Related issues

Resolves partially #703

[teresaromero]

test integrations

[elastic-vault-github-plugin-prod]

Created or updated PR in integrations repository to test this version. Check elastic/integrations#15689

[mrodm]

LGTM!
Just a doubt about the type used for Type field.-

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 7e723e3

History

• 💚 Build #1531 succeeded e079f63
• 💚 Build #1526 succeeded 97f7f13
• 💔 Build #1525 failed 4b7eefd

[mrodm]

Thanks!