Profiling: add data stream type

[inge4pres]

• data-streams: add profiling type
• test case for profiling data streams

What does this PR do?

We add a new data stream type profiling to allow creating dedicated data streams for Universal Profiling.

Why is it important?

We are going to use it in Cloud for the Universal Profiling symbolization service.

Checklist

• 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

[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-04-19T15:21:48.308+0000

• Duration: 8 min 54 sec

Test stats 🧪

Test	Results
Failed	0
Passed	762
Skipped	0
Total	762

🤖 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% (8/8)	💚
Files	70.37% (19/27)	👍
Classes	77.778% (28/36)	👍
Methods	55.172% (64/116)	👍
Lines	42.479% (593/1396)	👍
Conditionals	100.0% (0/0)	💚

[jsoriano]

There was a discussion about using the new profiling vs. the existing traces, and there it was also commented that this kind of event-like data would also fit in the logs type.

The main point of the discussion was to avoid having too many types of data streams.

Has there been some decision around this? Is it confirmed that logs cannot be used?

[inge4pres]

Has there been some decision around this? Is it confirmed that logs cannot be used?

I think so.

There is really no point in naming logs the profiling data.

[jsoriano]

Change looks good, will wait for @joshdover and @kpollich regarding the addition of the new type and its implications.

[kpollich]

Change looks good, will wait for @joshdover and @kpollich regarding the addition of the new type and its implications.

All good on my end.