feat(incident-io): add account_config.json with API key auth

[daniel-m-dd]

What does this PR do?

Add incident.io account config schema

Motivation

Add support for incident.io resources

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• 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

[datadog-datadog-us1-prod]

More details

Configuration file adds incident.io account authentication schema with API key bearer token support. Validation confirms valid JSON structure, correct field types, proper naming conventions, and full downstream consumer compatibility. No regressions identified.

Was this helpful? React 👍 or 👎

_{📊 Validated against 12 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit fb2de8c · What is Autotest? · Any feedback? Reach out in #autotest}

[yfangechiu]

nit: not sure how this renders but would Incident.io API Key be a bit long in the UI? Should we do label API Key and then set help to be incident.io API Key?

Review from yfangechiu is dismissed. Related teams and files:

• collaboration-integrations
  • incident_io/assets/account_config.json

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[leandroalmeida1997]

dont forget to promote the field once the asset is published.
you can read more in https://datadoghq.atlassian.net/wiki/spaces/WEBINT/pages/6877184047/Integration+Lifecycle+AMS+crawler-sdk+Schema+Validations#Adding-Fields-to-Existing-Integration-or-New-crawler-that-needs-new-field/dataflow