Add Doppler integration (ECOINT-6)

[nmanoogian]

What does this PR do?

This PR creates the Doppler log collection integration. This is an API-based integration that uses OAuth to connect Doppler with Datadog. Once connected, Doppler will begin sending activity log data to Datadog.

Motivation

What inspired you to submit this pull request?

Review checklist

• PR has a meaningful title or PR has the no-changelog label attached
• Feature or bugfix has tests (Not Relevant)
• Git history is clean
• If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
• If this PR includes a log pipeline, please add a description describing the remappers and processors.

[neko-dd]

Created DOCS-8635 for docs review

[michaelcretzman]

Approved with some minor edits.

[emarsha94]

The overview should include:
1 What does your product do in 1-2 sentences
2 What will customers get from this integration (the value of the integration & why it's helpful)
3 What specific data your integration monitors and the value?

[nmanoogian]

Thanks! I've updated this section with more of those specifics.

[emarsha94]

Can you please add clear directions a user would take to install the integration? For example, go to the Doppler tile on the integrations page, click connect accounts, you will be redirected to doppler to log in, ..

This should walk through the full oauth flow a user will take. I recommend testing the oauth flow and creating the steps on the steps you take!

[nmanoogian]

Absolutely, I re-tested the full oauth flow and provided more detail here.

[emarsha94]

please see here and follow steps above

[emarsha94]

please remove the agent_upgrade write scope from your oauth client and re-publish the client

[nmanoogian]

Done!

[emarsha94]

this is missing the submitted data type. Please add this https://docs.datadoghq.com/developers/integrations/check_references/#classifier-tags

[nmanoogian]

I've added the logs datatype

[nmanoogian]

Thanks all for the feedback!

A question for you: Do I need the files added in the "WIP: Add tests" commit? I re-ran ddev create and noticed that these came up.

I still need to let CI run and collect the test log results. I'll push again once that's done.

[nmanoogian]

Another question: What should I provide for these manifest values if our integration doesn't produce metrics or provide service checks:

{
  "assets": {
    "integration": {
      "metrics": {
        "prefix": [
          "Missing data for required field."
        ],
        "metadata_path": [
          "Missing data for required field."
        ]
      },
      "service_checks": {
        "metadata_path": [
          "Missing data for required field."
        ]
      }
    }
  }
}

[nmanoogian]

I've been able to resolve most of the validation errors with trial-and-error but I'm a little stumped on the outstanding issue with logs:

Facet path `type` conflicts with other integrations: crest_data_systems_fortigate, jfrog_platform, pan.firewall, vault. Please fix this conflict or change this facet definition to:
groups:
  - Event
name: Type
path: type
source: log