Integrate UI d2 python sdk into ttd data

[adithyasamavedhi-ttd]

UID2 integration into ttd-data Python SDK

Adds ttd_data.DataClient — the recommended top-level client for the
ttd-data SDK. It enables ingesting advertiser, third-party, offline-conversion,
and deletion-opt-out data to the Trade Desk Data API endpoints, and — when
a UID2Config is supplied — resolves raw PII (email / phone /
hashed_email / hashed_phone) into UID2 (or EUID) tokens via the UID2
IdentityMapV3Client SDK before the request leaves the process, then
forwards a UID2-only payload to the Trade Desk Data APIs.

The Speakeasy-generated client is treated as an internal building block.
It is not re-exported from the package root and callers should not use
it directly.

Files

File	Purpose (one line)
src/ttd_data/client.py	DataClient wrapper around BaseDataClient that wires the resolver into each endpoint via sub-SDK proxies and merges UID2 failures back onto failed_lines.
src/ttd_data/uid2/config.py	UID2Config dataclass + IdentityScope enum (UID2/EUID) holding base_url, api_key, client_secret.
src/ttd_data/uid2/models.py	Subclassed data items (AdvertiserDataItem, ThirdPartyDataItem, OfflineConversionDataItem, PartnerDsrDataItem) that add raw-PII fields, plus response wrappers that attach identity_resolutions.
src/ttd_data/uid2/resolver.py	The pre-request resolver: calls UID2 identity-map, mutates items in place (raw fields → UID2/EUID), and returns per-item resolutions + failed mappings.

ttd_data.DataClient, UID2Config, and IdentityScope are re-exported
from the package root. UID2-specific item / response classes live under
ttd_data.uid2.

Where to start reviewing

1. src/ttd_data/client.py — DataClient class docstring + the
   sub-SDK proxies show the request lifecycle (resolve → convert →
   request → merge → wrap).
2. src/ttd_data/uid2/resolver.py — module docstring covers the
   resolution rules, sentinel "*" behavior, and retry/abort policy.
3. src/ttd_data/uid2/models.py — see how subclass items extend the
   Speakeasy base models with raw-PII fields and a model_validator
   that enforces "at most one UID2-family identifier per item".
4. src/ttd_data/uid2/config.py — small, read this last.
5. Smoke-test entrypoint: data-api-local/test_uid2_ingest.py exercises
   all six wrapped endpoints end-to-end.

Flow / assumptions

• DataClient(uid2_config=None) is a thin pass-through over
  BaseDataClient — no UID2 work, same wire payload. Resolution only
  runs when a UID2Config is supplied.
• UID2 resolution runs at the Python boundary, before Speakeasy
  validates or serializes, so subclass-only raw fields aren't stripped.
• After resolution, raw PII fields are cleared on the item and only the
  resolved UID2/EUID (or TDID) is sent on the wire.
• Per-item unmapped identifiers → sentinel "*" substituted so line
  numbers stay 1:1; the Trade Desk Data APIs reject "*", and the SDK
  merges those rejections back into failed_lines with
  ErrorCode = "Uid2Error".
• Transient UID2 errors are retried (5x over 15s); catastrophic errors
  raise UID2ServiceError and abort the request entirely.
• The UID2 SDK itself normalizes raw emails (lowercase, gmail-specific
  . / + handling) and validates raw phones (E.164) before hashing —
  what travels to the operator is always SHA-256+base64 hashes, never
  plaintext.

Glossary of the key classes

• DataClient — top-level client for the ttd-data SDK; wraps
  BaseDataClient (the Speakeasy SDK) and, when uid2_config is
  supplied, adds UID2 resolution on the six PII-bearing endpoints.
• BaseDataClient — the raw Speakeasy-generated client; internal
  building block, not exported from the package root.
• UID2Config — credentials + scope (UID2 vs EUID) for the UID2 SDK.
• Sub-SDK proxy (_AdvertiserProxy, _ThirdPartyProxy, etc.) —
  thin per-area proxy exposed as client.advertiser, client.third_party,
  ... that runs resolve → convert → request → merge → wrap and falls
  through to the underlying Speakeasy sub-SDK for any unwrapped method.
• Subclassed data item (AdvertiserDataItem, ThirdPartyDataItem,
  OfflineConversionDataItem, PartnerDsrDataItem) — extends the
  Speakeasy base item with raw PII fields (email, phone,
  hashed_email, hashed_phone) that the resolver consumes; converted
  to the base item before the HTTP request is built.
• Response wrapper (IngestAdvertiserDataResponse, etc.) — wraps the
  Speakeasy response and attaches identity_resolutions so callers can
  inspect each raw id's resolved UID2 / unmapped reason.

Endpoints wrapped

• client.advertiser.ingest_advertiser_data
• client.third_party.ingest_third_party_data
• client.offline_conversion.ingest_offline_conversion_data
• client.deletion_opt_out.data_subject_request_advertiser_data
• client.deletion_opt_out.data_subject_request_merchant_data
• client.deletion_opt_out.data_subject_request_third_party_data

Each has a sync and _async variant. Any other Speakeasy method falls
through unchanged via __getattr__.

Tests:

1. advertiser

2. thirdparty

3. offline conversion

4. deletion-optout advertiser

5. deletion-optout thirdparty

6. deletion-optout merchant
   \

7. Test UserIdType Enum for offline conversions

8. Ensure that PII is dropped on the request to dataserver:

Check if its a breaking change for clients:

1. I created this script with some test entried of how clients can send data to various TTD Data APIs:
   local_data_api_ingest_e2e.py

2. I run the script on the current pypi version:

3. I run the script on this pr's sdk version: