Why aren't hydra and openapi3 generating the same components

[aymaneabssi]

Description
here I am testing the client generator and I am noticing that the hydra generates only this
`Interface for the "Book" resource type has been generated!

Interface for the "Review" resource type has been generated!

Interface for the "TopBook" resource type has been generated!`

and the openapi3 generate this:
`Interface for the "Book" resource type has been generated!;

Interface for the "Parchment" resource type has been generated!;

Interface for the "Review" resource type has been generated!;

Interface for the "TopBook" resource type has been generated!;
`

and when i looked at the endpoints on the api https://demo.api-platform.com/
i saw that there are 5
/books*
/parchments* // deprecated
/reviews*
/stats*
/top_books*

How to reproduce
I lunched the test-gen and test-gen-openapi3 commands

[alanpoulain]

Deprecated resources are filtered by default:
https://github.com/api-platform/create-client/blob/d791b8e316916a3e9db8005d08d090fd04b00c4f/src/index.js#L123
However the api-doc-parser should be able to mark the Parchment resource as deprecated as well:

api-doc-parser/src/openapi3/handleJson.ts

Line 124 in 895cd81

deprecated: !!pathItem.deprecated,

Transfering this issue to api-doc-parser. To investigate.