Preserve query parameters

@Neograph734 could you please reroll this as MR against 10.x?

aaron.ferris → made their first commit to this issue’s fork.

Hope im not stepping on anyones toes, but noticed some of these issues were quite old, so to keep them moving raised a quick MR - patch applied cleanly to 10.x.

Curiosity - what's the reason for cloning request when getting the query parameters? Would it no be sufficient to clone the query parameters if they are an object, or if it returns an array that would be copied anyway? I'm expecting some pointed to wild kernel level explanation of avoiding bad outcomes :D Actually, it was done this way in both patches so you may not be in the know.

Otherwise the patch looks like it should do what it should.

Yeah I also don't get the reason for the clone. We're just getting a value, don't we?

Yeah that did feel a little odd from the original patch, I’ll dig into it.

This was already fixed as part of 📌 Drupal 10 Readiness Fixed .
I removed the clone() method, it doesn't make any sense to me. If it's needed for any reasons, please teach me.