Fix query and path params not keeping the coerced types

[Fetchinator7]

This is to fix requests not saving with the correct types. ~~NOTE: This is only for query parameters, to my understanding path parameters are not being serialized at all. See line 307 in src/router.ts~~ ~~typescript { name: queryParam, in: 'query', },~~

Update: I realized coercing query parameters and path parameters use the exact same logic so I changed this to coerce both types. #144

[Fetchinator7]

~~I'm thinking we need a more robust way to parse booleans from strings Ok, I guess my question is; "If the input parameter string is not a boolean, how should we handle that in the parser?" For example, parseJSON(input.toLowerCase()) would return the appropriate boolean or undefined if the input is anything besides those strings, but if the input isn't a boolean what would we do? Would we throw an error here in the parser? From my understanding, validating request inputs happens elsewhere with ajv (or whatever is implemented) and this is only for parsing the requests. So, if the input is invalid/not a boolean is it the responsibility of this parser to throw an error? This works correctly for the happy cases, so what should happen in the unhappy cases that would allow us to implement "a more robust way to parse booleans"?~~

[lgtm-com[bot]]

This pull request introduces 1 alert when merging 1ab18a75f9ec9b36e67acea275e49089eb70693f into 2d7a470aee1117034ea77fd68c4cf9aeaec0f749 - view on LGTM.com

new alerts:

• 1 for Useless assignment to local variable

[nklisch]

@anttiviljami Do we expect a fix, like this PR is suppose to address, likely to happen? Does this PR need to be updated? As I see it is a year old?

[anttiviljami]

Superceded by #571