[ECS][lyve_cloud] Correcting invalid ECS field usages at root-level

[kgeller]

What does this PR do?

Correcting invalid ECS os.name field usages at the root-level. We already have the information at a correct location user_agent.os.name , so this is only a deletion.

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

• Relates Invalid ECS field usages at root-level #7808

[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-09-26T15:48:26.682+0000

• Duration: 15 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5
Skipped	0
Total	5

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	100.0% (2/2)	💚
Classes	100.0% (2/2)	💚
Methods	86.364% (19/22)	👎 -10.303
Lines	87.273% (192/220)	👎 -12.727
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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

[taylor-swanson]

LGTM

[elasticmachine]

Package lyve_cloud - 1.8.0 containing this change is available at https://epr.elastic.co/search?package=lyve_cloud