Support object parameter and fix optionals

[alex-fusionauth]

I had to create new PR to update the old #37 to the latest codebase sorry @ianwensink.

I think this makes sense as most of the time in JS you will pass objects on the create.

[lyleschemmerling]

It's an interesting idea to solve the problem that the typescript typings are not correct, however, there's more that we will need to take into account.

The file FusionAuthClient.ts is generated. The source for that is here. Any changes made to this file directly will be over-written the next time we run the generator.

But that also means we do have the opportunity to address all of the methods in the client at once. We do need to maintain backwards compatibility, which this does, and we want to ensure that the pattern is consistent and sensible for the whole of the client. So if we want to make this change we will need to make it in the builder file and then ensure that it makes sense once it is built.

One issue we will want to consider when addressing this is that the JSON files which are the source for the client builder have "(Optional)" in the comments for the parameters but there isn't an explicit property declaring the parameter as optional, we should look into that because we should get the typings to indicate where they are optional correctly regardless of if we are passing an object or positional parameters