[Bug][OpenAPI] Deprecated properties display in response examples

[nateKlaux]

Describe the Bug

OAS 3.1.x supports a deprecated tag, which Fern correctly applies to the schema. However, in Response Examples, deprecated properties still appear even when they are not defined in the OAS definition.

This results in inaccurate examples that may mislead customers.

Information to Reproduce

CLI Version

"version": "0.45.0-rc52"

Actual Behavior

Expected Behavior

For properties where deprecated: true not to render in response examples.

API Definition (if relevant)

In Example 1 below:

• The customAddress array is null, but the rendered response example still incorrectly includes categoryName.
• The chainalysisIdentification array is not null but does not define a categoryName example, yet the rendered response example still incorrectly includes categoryName.

              examples:
                example1:
                  summary: Example 1
                  value:
                    - asset: ETH
                      address: "0xC8a65Fadf0e0dDAf421F28FEAb69Bf6E2E589963"
                      cluster:
                        name: "PolyNetwork Hack 2021-08-10"
                        categoryId: 6
                      rating: "lowRisk"
                      customAddress: null
                      chainalysisIdentification:
                        addressName: "STOLEN FUNDS: PolyNetwork Hack 2021-08-10"
                        description: ""
                        categoryId: 6