fix(templates): ensure requestOptions follow same format

[shortcuts]

🧭 What and Why

🎟 JIRA Ticket: -

Changes included:

Changes in this PR were added in #501, but are unrelated to the task.

Java/JavaScript:

• Fix type for queryParameters

Java/JavaScript/PHP:

• Ensure requestOptions.queryParameters are handled the same way than method queryParameters

PHP:

• Remove hardcoded case for array query parameters, they should all be treated the same way

🧪 Test

CI :D

[netlify]

✅ Deploy Preview for api-clients-automation canceled.

Name	Link
🔨 Latest commit	8fc5b3d
🔍 Latest deploy log	https://app.netlify.com/sites/api-clients-automation/deploys/6283685b603b8b00082d57ff

[algolia-bot]

✗ The generated branch has been deleted.

If the PR has been merged, you can check the generated code on the main branch.

[millotp]

Nice ! I'm not entirely sure of when query params should be stringified, should it be last second before creating the URL, or as soon as we receive them they get stored as string ?

[shortcuts]

Nice ! I'm not entirely sure of when query params should be stringified, should it be last second before creating the URL, or as soon as we receive them they get stored as string ?

I've went with what was the easiest for the current implem to avoid changing everything, I feel like to avoid redundancy it's best to apply it when we will use them rather than in every methods

[damcou]

Nice improvement ! I reviewed and tested the changes on my local env and it works fine ! :)

[millotp]

I don't understand how we can get object here

[shortcuts]

const requestOptions = {
  queryParameters: {
    myParam: { a: 'b' },
  },
}

idk if we should allow this in JS but as it's the case in the current client, we can keep the same logic

[millotp]

I'm not sure about all this but let's go