fix(state): object mapper with list<object>

[senaria]

Q	A
Branch?	4.2
Tickets	Closes #7563
License	MIT
Doc PR	N/A (bug fix, no doc changes)

Description
Fix ObjectMapperProvider to correctly handle unpaginated collections (arrays) when using stateOptions with the Map attribute.

Problem
When using GetCollection with pagination=false (or paginationEnabled: false), the ObjectMapperProvider was skipping the object mapping because it only checked for is_object($data). Arrays returned by unpaginated collection endpoints were not being mapped, causing serialization errors like:

Can't get a way to read the property "X" in class "Entity"

Solution
The fix separates the early-return conditions:

First check if mapping should be skipped entirely (no objectMapper or operation cannot map)
Then check if the data type is mappable (object or array)
For arrays, the provider now maps each element using array_map(), similar to how paginated collections are handled.

Changes
Modified ObjectMapperProvider::provide() to handle array data
Added unit tests for ObjectMapperProvider covering all scenarios (single object, paginated, unpaginated, empty cases)
Added functional test (Issue7563Test) demonstrating the fix with a real API endpoint

[senaria]

Not sure why half of the stuff fails, but seem to be unrelated to my changes, looking at it. I ran cs-fixer on my files and obviously check the tests locally.

If this blocks it getting merged I would love to get some infos how I get all of these checks green.

[senaria]

@soyuka this PR might interest you since I saw you doing stuff on the ObjectMapperProcessor.

[soyuka]

Thanks!