fix: correctly handle form and file parameters as requestBody instead of query parameters

[VanHai1424]

Issue:
When generating OpenAPI specs, parameters with in value form or file were incorrectly treated as query parameters, causing unexpected parameter objects to appear in the output.

Cause:
The original code used an if condition which didn't clearly separate handling of parameters by their location, leading to form and file parameters being processed as query parameters.

Solution:
Refactor the code to use a switch statement on the parameter’s in value to explicitly handle:

• form and file parameters by calling appendRequestBody (adding them to requestBody content as form data),

• body parameters by calling parseRequestBody,

• Other parameters (query, path, etc.) by calling appendQueryParam.

[parvez3019]

Hi, thanks for your valuable contribution. Can you add unit tests and integration tests for the same? so that we can merge this?

[VanHai1424]

Hi, I have added the unit tests and integration tests as requested. Please review them and let me know if any further changes are needed. Thanks!