feat: add optional creator_email, updater_email, team_name to Metric Sync API payload

[bertilhatt]

Summary

Adds support for the new optional Metric Sync API fields: creator_email, updater_email, and team_name at both sync-level and per-metric level. Sync-level values apply as defaults to all metrics; individual metrics can override via dbt meta keys.

Resolves: FFESUPPORT-407

Dependency: This work depends on the Metric Sync API changes in Eppo-exp/eppo — PR #13697. That PR augments the API to accept these optional body fields and defines semantics (omit = clear, lookup failure = clear, per-metric overrides). This PR updates dbt-eppo-sync to send the new fields when configured.

---

Changes

1. Mapper (mapper.py)

• Sync-level: map_dbt_to_eppo_sync_payload() now accepts optional creator_email, updater_email, and team_name. When provided, they are included in the top-level request body next to sync_tag, fact_sources, and metrics. When omitted, the keys are not sent (API treats omit as clear).
• Per-metric: For each metric, the mapper reads from meta:
  • eppo_creator_email → creator_email
  • eppo_updater_email → updater_email
  • eppo_team_name → team_name
    Only metrics that define these in meta get the corresponding keys on their object; others rely on sync-level defaults on the API side.

2. Sync orchestration (sync.py)

• run_sync() accepts optional creator_email, updater_email, and team_name and passes them through to the mapper.

3. CLI (cli.py)

• New options: --creator-email, --updater-email, --team-name.
• Config file: Optional sync config is read from dbt_project.yml:
  • Top-level key eppo_sync, or
  • vars.eppo_sync
    Supported keys: creator_email, updater_email, team_name. CLI options override config file values when both are set.

4. Schema (eppo_metric_schema.json)

• Top-level optional properties: creator_email, updater_email, team_name (with descriptions and format/length constraints).
• Under metrics.items: same three as optional per-metric properties.

5. Tests

• test_mapper.py: test_map_sync_level_creator_updater_team, test_map_sync_level_omit_optional_metadata, test_map_per_metric_override_creator_team.
• test_sync.py: test_run_sync_passes_creator_updater_team_to_mapper, and assertions in test_run_sync_successful_live that mapper is called with the new params (as None when not provided).

---

Usage

CLI (overrides config):

dbt-eppo-sync --dbt-project-dir . --manifest-path target/manifest.json \
  --creator-email "data-team@company.com" \
  --updater-email "ci-bot@company.com" \
  --team-name "Analytics"

Config in dbt_project.yml:

eppo_sync:
  creator_email: "data-team@company.com"
  updater_email: "ci-bot@company.com"
  team_name: "Analytics"

Per-metric override in dbt metric YAML:

metrics:
  - name: my_metric
    label: My Metric
    type: sum
    measure: { name: revenue }
    meta:
      eppo_creator_email: "analyst@company.com"
      eppo_team_name: "Growth"

---

Checklist

• Sync-level and per-metric fields implemented and only sent when set.
• CLI options and dbt_project.yml config support.
• Schema updated; validation continues to pass.
• Tests added/updated for mapper and run_sync.