Add support for syncing archived entities (ENTITY_STATUS_ARCHIVED) across core DV360 objects (Campaigns, Insertion Orders, Line Items, Creatives, and Ad Groups).

1. Problem Statement

The DV360 connector currently omits archived entities. During historical or initial syncs, any campaigns, insertion orders, line items, or creatives that clients have archived do not populate in the destination warehouse.

2. Technical Context

By default, DV360 API .list endpoints (displayvideo.advertisers.lineItems.list, campaigns.list, etc.) explicitly exclude records where entityStatus equals ENTITY_STATUS_ARCHIVED unless passed in the filter parameter.

Furthermore, the DV360 API enforces an "at most one restriction" constraint on the entityStatus field, meaning a single request cannot evaluate OR conditions across multiple statuses (e.g., entityStatus="ENTITY_STATUS_ACTIVE" OR entityStatus="ENTITY_STATUS_ARCHIVED" is invalid). Because of this API restriction, archived entities require a distinct query pass (filter="entityStatus=\"ENTITY_STATUS_ARCHIVED\"") to be retrieved.

3. Business Impact

• Historical Reporting Gaps: Media teams routinely archive completed campaigns and line items as standard hygiene. Because these are omitted during the initial sync, historical reporting, budget reconciliation, and multi-year trend analysis are incomplete.

• Data Discrepancies: Warehouse reporting does not match the DV360 UI or CM360 cross-channel data, undermining client trust in automated ETL pipelines.

• Onboarding Friction: We cannot provide reliable end-to-end reporting for newly onboarded clients whose historical data contains archived structures.

4. Proposed Solution

• Introduce a configuration toggle in the connector setup: "Include Archived Entities" (enabled by default or optional).

• Under the hood, have the sync pipeline perform an additional query pass using filter="entityStatus=\"ENTITY_STATUS_ARCHIVED\"" to ingest past entities alongside active and paused records.