[BUG] Inference specification 2025-03-01-preview is not valid in APIM

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cognitiveservices/data-plane/AzureOpenAI/inference/preview/2025-03-01-preview/inference.json

### API Spec version

2025-03-01-preview

### Describe the bug

We use the API specifications in our AI-Gateway company solution. All the previous versions would work out of the box and we could import them into the published API. This version is suddenly openapi version 3.1.0 and does not work out of the box as there are issue reported by APIM when adding the specification.

### Expected behavior

It should be possible to import this api spec into API in APIM without issues or modifications.

### Actual behavior

We get this issues reported with the file:

`One or more fields contain incorrect values:
Parsing error(s): $recursiveAnchor is not a valid property at #/components/schemas/CompoundFilter [] $recursiveRef is not a valid property at #/components/schemas/CompoundFilter/properties/filters/items/oneOf [] Cannot create a scalar value from this type of node. [#/components/schemas/createResponse/allOf/properties/include/description] propertyNames is not a valid property at #/components/schemas/VectorStoreFileAttributes []
Parsing error(s): The input OpenAPI file is not valid for the OpenAPI specification https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md (schema https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v3.0/schema.yaml).`

### Reproduction Steps

Try to update api specification of an API in APIM.

### Environment

We run AI Gateway architecture solution with APIM serving as a centralized AI Gateway with Azure AI instances in the backend.

Start with specification/cognitiveservices/data-plane/AzureOpenAI/inference/preview/2025-03-01-preview/inference.json and reproduce the import in APIM. Compare it with earlier inference specifications and inspect the reported OpenAPI 3.1, $recursiveAnchor, $recursiveRef, propertyNames, and description errors. Done means APIM imports the specification without modifications or parsing errors.

Written by the indexing model from the issue text.