Add dataflow definitions for opentelemetry

[alexeypilyugin]

Add missing dataflow declarations inferred from integration source/config for logs, metrics, and events where applicable.

What does this PR do?

Adds dataflows to agent integrations based on the following rules:

• Owned by opentelemetry
• Doesn't have a dataflows definition yet
• Dataflow is in the following format %integration-name%-%dataflow-type%, where dataflow-type can be one of [logs, metrics, events]
• direction is always inbound
• always_on is true if the flow cannot be turned off once the conf.yaml is set up. For example, metrics are usually always_on: true because they cannot be turned off once the configuration is in place. Logs, however, are always_on: false because log collection can be disabled in the conf.yaml file.

Motivation

https://datadoghq.atlassian.net/wiki/spaces/IXP/pages/5756519690/Describing+your+Integration+Dataflows

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[asopkin]

Hey! Adding the assets/no-deploy label to this PR temporarily so I can get a dashboard for mine deployed to staging: #22861