generate-config produces invalid configuration - DraftDataset with blank org

[rustyjux]

Description

When using gwa generate-config interactively, if org/orgunit are left blank, then they are blank in the created DraftDataset and validation fails when publishing.

organization: 
organizationUnit:

Meanwhile, if parameters are provided (e.g.
gwa generate-config --template quick-start --service <MYSERVICE> --upstream https://httpbin.org) then org/orgunit are autofilled with:

organization: ministry-of-citizens-services
organizationUnit: databc

org and orgunit are optional fields (ie you can omit those fields and still add/update a dataset), but they cannot be blank.

Acceptance criteria

• review the default behaviour for org/orgunit.
  • Interactive and template use should behave the same (use same defaults, never leave blank fields in yaml)
  • Possible approaches include:
    • provide default values (CITZ/databc) to interactive, hit ENTER to accept
    • OR do not have default values, publish dataset without org/orgunit if not provided
• always produce valid output from generate-config
  • do not create DraftDataset where organization and organizationUnit are blank which will fail validation