Missing `ConvertDateToLocalTimezone` parameter on `TypeScriptClientGeneratorSettings` and `OpenApiToTypeScriptClientCommand`

[gabrielheming]

Describe the bug

Following this PR, the parameter ConvertDateToLocalTimezone was added to configure whether the DateOnly conversion should be to local or no. However, the parameter does not exists on the settings TypeScriptClientGeneratorSettings and also does not exists on OpenApiToTypeScriptClientCommand.

The lack of that configurable makes it impossible to work with DateOnly parameters when the native Date object is being used and the current user is on negative timezone offset.

Version used

Tested with version 14.2.0 from npm

Expected behavior

When this parameter is set to true, DateOnly conversion should use the method parseDateOnly that converts the Date to the local time zone.

[AlexPaven]

Yep I just hit this and it makes me very sad. Will try to find the time to open a PR.

[gabrielheming]

For those who are struggling with this issue, you can replace the current liquid template with your desired approach.

I've created the template with the precise name File.FormatDate.liquid, using the following code (which is slightly different from the one at the parseOnly template)

function formatDate(d: Date) {
    return d.toISOString().slice(0, 10);
}

As I use the '.json' configuration file, I've set the template folder's path as following (extra configurations omitted):

{
  "codeGenerators": {
    "openApiToTypeScriptClient": {
      "templateDirectory": "src/nswag/templates"
    }
  }
}

That does the workaround when generating the source code.