Update (most) obs-cloud-monitoring owned packages to format_version 3.0.0

[tommyers-elastic]

This PR updates all obs-cloud-monitoring owned packages, except azure and azure_metrics, to package spec v3.

These changes are mostly autogenerated in three stages.

1. Firstly we run elastic-package format on everything. This commit can be excluded from review to make the diff cleaner.

2. Then the following yq commands are run across all the affected packages:

find $1/data_stream -type f -path "*fields*" -name "*.yml" -exec yq e -i "del .[].release" {} \;
find $1/data_stream -type f -path "*fields*" -name "ecs.yml" -exec yq e -i "unique_by(.name)" {} \;
yq e -i 'del .release' manifest.yml
yq e -i "with(select(.license != null); .conditions.elastic.subscription = .license) | del .license" manifest.yml

3. Next the ecs-update tool is run as follows:

go run github.com/andrewkroh/go-examples/ecs-update@main -format-version=3.0.0 -fix-dotted-yaml-keys -add-owner-type -owner elastic/obs-cloudnative-monitoring packages/*

Any remaining issues were fixed manually. Even though most of the changes here were generated by tooling, this still needs careful review (hide whitespace changes to make your life easier).

There should be no functional changes to any of the packages here.

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.

[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-10-13T15:44:02.024+0000

• Duration: 25 min 58 sec

Test stats 🧪

Test	Results
Failed	0
Passed	37
Skipped	0
Total	37

🤖 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% (1/1)	💚
Classes	100.0% (1/1)	💚
Methods	66.667% (14/21)	👍 3.252
Lines	100.0% (135/135)	💚 0.137
Conditionals	100.0% (0/0)	💚

[zmoog]

LGTM.

@tommyers-elastic, do you plan to address the platformlogs' _dev/test/pipeline/test-platformlogs-invalid-raw.log malformed JSON issues on in a different PR?

IIRC, the test fails on stack versions > 8.6 because the json processor in Elasticsearch has become stricter by default starting from 8.7.

More on this issue at zmoog/public-notes#54

[tommyers-elastic]

hey @zmoog yeh i have another PR just for azure because it contains quite a few more changes. i haven't addressed the malformed log issue there yet, but i will get round to it soon.

[zmoog]

@tommyers-elastic, I mentioned it so we do not forget it. Happy to help with a review!

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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

[elasticmachine]

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