Support object input for overrides

I wonder if there isn't a need for an object type input something like:

[
  {
    "URL:": "https://example.com/1.exe",
    "Scope": "user",
    "Architecture": "x64",
    "DisplayVersion": "1.2.3_64"
  },
  {
    "URL:": "https://example.com/2.exe",
    "Scope": "user",
    "Architecture": "x86",
    "DisplayVersion": "1.2.3_86"
  },
  {
    "URL:": "https://example.com/3.msi",
    "Scope": "machine",
    "DisplayVersion": "1.2.3"
  },
]

Treat it the same way you would an override for a URL, but then it's a bit more "user-friendly" for autonomous updates, since the workflow could build up a single object to pass in

Originally posted by @Trenly in https://github.com/microsoft/winget-create/issues/516#issuecomment-1953125293

No file or test is named in the issue. Start by locating the existing URL override input path and compare it with the shown array of objects; done means object input is accepted and treated like a URL override for the listed fields, with coverage for the examples.