[Netflow] Missing ECS Field Mappings

[MakoWish]

Type of change

• Bug

What does this PR do?

This PR adds missing mappings source.* and destination.* fields to prevent field mapping conflicts in the logs-* Data View.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have incremented the version in my package's manifest.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Related issues

• Closes [Netflow] Missing ECS Field Mappings #7270

Screenshots

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-08-10T00:55:10.844+0000

• Duration: 15 min 22 sec

Test stats 🧪

Test	Results
Failed	0
Passed	14
Skipped	0
Total	14

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[efd6]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	100.0% (9/9)	💚
Lines	92.0% (92/100)	👎 -0.026
Conditionals	100.0% (0/0)	💚

[ShourieG]

LGTM

[efd6]

Please hold off on merging this subject to internal discussion.

[efd6]

The approach that we should be using here is to turn on import_mappings. This is ~detailed here in the package spec, but there is an issue to improve the documentation for the option here. There are examples of its use in the wild, for example here.