test(jsonld): type inconsistency when using itemUriTemplate (#7650)

Author: soyuka

CHANGELOG.md

@@ -7,6 +7,10 @@
 * [21aa2572d](https://github.com/api-platform/core/commit/21aa2572d8fef2b3f05f7307c51348a6c9767e45) feat(elasticsearch): add SSL options for Elasticsearch configuration (#4059)
 * [ba0c76c](https://github.com/api-platform/core/commit/ba0c76c6f5c8afa8622e87a155b8b99f453d6453) feat(doctrine): remove put & path for readonly entity (#7019)
 
+### Breaking changes
+
+* When using `output` with `itemUriTemplate` on a collection operation, the JSON-LD `@type` will now use the resource class name instead of the output DTO class name for semantic consistency with `itemUriTemplate` behavior.
+
 ## v4.2.11
 
 ### Bug fixes

features/jsonld/input_output.feature

@@ -379,6 +379,7 @@ Feature: JSON-LD DTO input and output
     Then the response status code should be 200
     And the response should be in JSON
     And the header "Content-Type" should be equal to "application/ld+json; charset=utf-8"
+    Then print last JSON response
     And the JSON should be valid according to this schema:
     """
     {
@@ -400,7 +401,7 @@ Feature: JSON-LD DTO input and output
             "required": ["@id", "@type", "foo", "bar"],
             "properties": {
               "@id": {"pattern": "/dummy_foos/bar"},
-              "@type": {"pattern": "^DummyCollectionDtoOutput$"},
+              "@type": {"pattern": "^DummyFooCollectionDto$"},
               "foo": {"type": "string"},
               "bar": {"type": "integer"}
             }