Add Channel-Based Market Conditions and New Error Codes

The API now introduces a ChannelsCondition object that lets you evaluate whether a visitor’s channel matches a market’s criteria, and an input object MarketConditionsChannelsInput for passing channel IDs when creating or updating such conditions. The Channel type gains three new fields: activeRegions, markets (a paginated list of Market objects), and marketsCount, allowing clients to inspect a channel’s active geographic regions and the markets it belongs to. Correspondingly, the Market type receives channels, channelsCount, and is linked back to its associated channels. The enums MarketConditionType and MarketType now support a new CHANNEL value, enabling channel-specific condition types and market types. MarketConditions now includes a channelsCondition field, exposing the new channel-based condition structure. Additional error codes—INVALID_CHANNEL_IDS, CHANNEL_MARKET_MUST_HAVE_SINGLE_CHANNEL_DRIVER, CHANNEL_NOT_VALID_FOR_CHANNEL_MARKET, CHANNEL_DRIVER_MUST_HAVE_CHANNEL_SPECIFICATION, and REGION_NOT_SUPPORTED_FOR_CHANNEL—are added to MarketUserErrorCode to reflect validation rules when managing channel markets. Together, these changes empower developers to create, query, and validate markets that are explicitly tied to specific channels and regions while handling new error scenarios in API calls.