feat: add supported and unsupported_reason fields to pricing options

[bokelley]

Summary

• Add supported: bool | None and unsupported_reason: str | None fields to all pricing option types
• Create shared PricingOptionBase class to avoid code duplication
• Bump version to 2.13.1

Context

Sales agents need to annotate pricing options at runtime to indicate whether each option is supported by the current adapter. Currently this causes mypy errors because these fields don't exist on the types.

Changes

The following pricing option types now inherit from PricingOptionBase:

• CpmFixedRatePricingOption
• CpmAuctionPricingOption
• VcpmFixedRatePricingOption
• VcpmAuctionPricingOption
• CpcPricingOption
• CpcvPricingOption
• CpvPricingOption
• CppPricingOption
• FlatRatePricingOption

The new fields:

• Default to None (not included in responses unless explicitly set)
• Are optional (not required)
• Work with extra='forbid' config (they're defined fields, not extra)

Test plan

• All 344 existing tests pass
• Verified fields serialize correctly (omitted when None)
• Verified inheritance is correct for all pricing option types

🤖 Generated with Claude Code

[youbek]

I'm bit confused why we are only getting 2 union types for async-response-data.json when it is also has a union of all intermediate response types.

So should we also do such mapping for other new union types such as CreateMediaBuyAsyncInputRequired?

Or is it because final response types such as CreateMediaBuyResponse has a unnamed union types?
If this is the case, did we had similar mapping/fixing previously? Because I haven't touched the CreateMediaBuyResponse's schema.

[youbek]

Ok. Yes my union schema i added (async-response-data.json) was the main reason. But think I was able to get correct results with simpler change. Here's the PR. Just removed --collapse-root-models when generating types. Let me know what you think about this

[youbek]

Here's the claude explanation of why this fixes it:

 Why This Caused the Deletion

  The issue occurs when you have nested unions (a union that references another union):

  async-response-data.json (has anyOf)
    ├─► References: create-media-buy-response.json (has oneOf)
    ├─► References: update-media-buy-response.json (has oneOf)
    └─► References: sync-creatives-response.json (has oneOf)

  With --collapse-root-models ON:

  1. Generator processes create-media-buy-response.json:
    - Sees: Root-level oneOf
    - Thinks: "Should I collapse this?"
    - Decision: "Let me check if it's used elsewhere first..."
  2. Generator sees it's referenced in async-response-data.json:
    - Sees: async-response-data.json has its own anyOf that includes this schema
    - Thinks: "This schema is being used in another union"
    - Decision: "I'll collapse it AT THE USE SITE, not at the definition site"
  3. Result:
    - The "collapsed" version lives in the parent union (async-response-data)
    - Original file gets ONLY the variant classes (CreateMediaBuyResponse1, CreateMediaBuyResponse2)
    - The wrapper class CreateMediaBuyResponse is DELETED

  With --collapse-root-models OFF:

  1. Generator processes create-media-buy-response.json:
    - Sees: Root-level oneOf
    - Generates: RootModel wrapper + variants
    - Decision: "Always generate wrappers, don't collapse"
  2. Generator sees it's referenced in async-response-data.json:
    - Sees: async-response-data.json includes this schema
    - Thinks: "The type already exists, just import it"
    - Decision: "Use the existing RootModel wrapper"
  3. Result:
    - Original file KEEPS its wrapper class
    - Parent union just references it
    - Everyone's happy ✓
    ```