[BUG] ORD plugin injects x-sap-api-type: ODATAV4 into OpenAPI spec for REST-protocol services

[S3lected]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

A CAP service annotated with @protocol: 'rest' and apiProtocol: 'rest' in @ORD.Extensions still gets x-sap-api-type: ODATAV4 and x-odata-version: 4.01 injected into its generated OpenAPI spec.

The ORD document correctly reflects "apiProtocol": "rest", but the OpenAPI doc contradicts it — creating inconsistent metadata for API consumers.

Expected Behavior

For @protocol: 'rest' services, no OData-specific extensions should appear in the OpenAPI output.

Steps To Reproduce

No response

Versions

No response

OS / Environment

Linux

Repository Containing a Minimal Reproducible Example

No response

Anything else?

No response