Options have String values that are `boolean-type`

There are some options on different languages that are string-type but the default values are boolean-type ( "true"/"false" ).
I think since there are no limitations on using the boolean type, why not change these options to corresponding types to maintain consistency.

Options for Go language for a V3 Client, using the online generator ( https://generator3.swagger.io/api/options?language=go&version=V3 ):

{
  "packageName": {
    "opt": "packageName",
    "description": "Go package name (convention: lowercase).",
    "type": "string",
    "default": "swagger"
  },
  "hideGenerationTimestamp": {
    "opt": "hideGenerationTimestamp",
    "description": "Hides the generation timestamp when files are generated.",
    "type": "string",
    "default": "true"
  },
  "packageVersion": {
    "opt": "packageVersion",
    "description": "Go package version.",
    "type": "string",
    "default": "1.0.0"
  },
  "withXml": {
    "opt": "withXml",
    "description": "whether to include support for application/xml content type and include XML annotations in the model (works with libraries that provide support for JSON and XML)",
    "type": "boolean",
    "default": "false"
  }
}

The hideGenerationTimestamp option is a String with a boolean-type value by default ( "true" ), but we also have the option withXml that is boolean type with a default value of "false".

Start with the generator options endpoint linked in the issue and locate the definitions of hideGenerationTimestamp across the affected language generators. Compare its declared type and default with the boolean withXml option, then verify that the affected options consistently expose boolean types and boolean defaults.