[azure] Fix event.duration field conflict in log data streams

[legoguy1000]

What does this PR do?

Fix event.duration field conflict in Azure Logs.

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 verified that Kibana version constraints are current according to guidelines.

Related issues

• Closes [azure] mapping conflict event.duration #2887

[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: 2022-03-29T14:32:54.252+0000

• Duration: 11 min 55 sec

Test stats 🧪

Test	Results
Failed	0
Passed	85
Skipped	0
Total	85

🤖 GitHub comments

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

• /test : Re-trigger the build.

[andrewkroh]

I think the version needs bumped to 1.1.3 to correct the merge conflicts.

[andrewkroh]

/test

[kaiyan-sheng]

Thanks for fixing this! I see this field is also missing in the other azure log data streams. Do you mind adding them in the same PR 🙂 ? If not, I can add the rest in a separate PR too. Thanks again!!

[legoguy1000]

Thanks for fixing this! I see this field is also missing in the other azure log data streams. Do you mind adding them in the same PR 🙂 ? If not, I can add the rest in a separate PR too. Thanks again!!

No problem.

[legoguy1000]

@kaiyan-sheng done

[andrewkroh]

/test

[andrewkroh]

I fixed a merge conflict with another PR that I merged in and changed the version to 1.1.4.

[kaiyan-sheng]

Seems like the CI is not happy 😬 Could you rerun the test to generate the expected json files please? Thanks!!

[andrewkroh]

Oh, it's probably the new forwarded tags from the other PR that recently merged.

[legoguy1000]

looks like it was the static data files.