Ensure toJson and toResponse call jsonSerialize

[clementbirkle]

Description

I noticed that the toJson() and toResponse() methods do not use the jsonSerialize() method.

This can be problematic in certain use cases. For example, you might override jsonSerialize() to transform an empty array into an object to ensure consistent data structures on the frontend.

With this PR, the package will be more aligned with Laravel's behavior, which respects the jsonSerialize() method in similar scenarios.

Example

$data = new class extends Data
{
    public function __construct(
        public array $customFields = [],
    ) {}

    public function jsonSerialize(): array
    {
        $array = parent::jsonSerialize();

        // Ensure customFields is always an object
        $array['customFields'] = (object) $array['customFields'];

        return $array;
    }
};

// Current behavior:
json_encode($data);           // {"customFields":{}}
$data->toJson();              // {"customFields":[]}
$data->toResponse(request()); // {"customFields":[]}

// With this PR:
json_encode($data);           // {"customFields":{}}
$data->toJson();              // {"customFields":{}}
$data->toResponse(request()); // {"customFields":{}}

As shown, json_encode($data) and $data->toJson() currently produce inconsistent results. This PR fixes that.

Implementation Note

To make toResponse() respect jsonSerialize(), I introduced a new method: jsonSerializeWithTransformationContext(). This method may also be useful in other parts of the package, such as:

• Livewire integration
• Possibly other areas as well?