Don't generate a Content-Location on GET responses

[dunglas]

Currently, API Platform adds a Content-Location header on responses to GET requests that has the exact same value as the requested URL.
While this is valid (https://httpwg.org/specs/rfc9110.html#field.content-location), this is useless and can cause weird issues, for instance when the serialized resource doesn't contain an ID (temporarily response, preview...).

We should not generate this header for responses to GET requests.

[soyuka]

mhh but #6627 and #6625 ping @darkweak

[darkweak]

You can rollback IMHO @soyuka, I'll find another way to get the location on list. Thank you for implementing this for this short time. 😄