NOISSUE Remove request body from GET requests

[mglowala]

Production issue

Daily pickup point import in tamago started failing today:

InPost backend (behind Cloudflare) now rejects GET /v1/points when the request carries a body:

• with Content-Type: application/json → HTTP 400 "Your client has issued a malformed or illegal request"
• without Content-Type → HTTP 502 from Cloudflare

Reproduced from the cron pod by replaying the exact Guzzle request:

curl -X GET 'https://api-shipx-pl.easypack24.net/v1/points?type=parcel_locker_only&per_page=500&page=1&fields=...' \
  -H 'User-Agent: GuzzleHttp/7' -H 'Content-Type: application/json' \
  --data-raw '{"searchCriteria":{...}}'
→ 400 Bad Request

The same URL without body returns 200. Bisection confirmed body in GET is the sole trigger - all individual headers (UA, Content-Type, etc.) are fine on their own.

Fix

FindPoints::findPoints was serializing the whole FindPointsRequest into the body of a GET request, duplicating data already passed via query string. RFC 9110 says clients SHOULD NOT send a body in GET; InPost / Cloudflare just started enforcing it.

• Drop the body and Content-Type header from the HttpRequest in FindPoints.
• Remove Serializer from FindPoints::__construct (no longer needed).

Test

Added findPointsSendsGetRequestWithoutBody regression test asserting the outgoing request is GET, has empty body and no Content-Type header.

[lukasz-falda]

Prosiłbym jednak w opisie dwa/trzy zdania o tym co jest robione (po ludzku). Taki elaborat to sobie sam dopowiem jak review zrobię 😛