feat(json-schema): mutualize json schema between formats

[soyuka]

Q	A
Branch?	main
Tickets	starts fixing #6485
License	MIT

Instead of generating twice a definition for 2 different formats, we generate the json one and reference the json format inside the jsonld format:

https://gist.github.com/soyuka/20d0d216c3fce1b68165dbbf58381e02

When generating a single resource on our TestBundle we lower the OpenAPI file size quite a bit:

• 12K on 4.1
• 8.0K with this patch

Left to be done:

• check if serialization groups work
• fix feat(jsonschema): make JSON-LD specific properties required only in the schema for output #6485
• tests

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ttskch]

@soyuka Thank you for the great job!

[vinise]

@soyuka
We are now using "allOf" to combine based and specific schemas.
this is not a real inheritance, just combine all schemas with no precedence (at least, I understand it like that)

For HydraCollectionBaseSchema this seems problematic, as it defines a property "member" with a simple "object" type (no specific type specified)
On a collection object, the property "member" is redefined with correct typing.

As order should not impact the schema, client generation libraries have no idea of which "member" definition to take
for ex "heyapi" is even generating a member with 2 possible type

Shouldn't we remove member definition from HydraCollectionBaseSchema ? and keep only the correct full typed one ?