Improve import command with install/add functionality on a per-package basis

Description of the new feature / enhancement

I was surprised to see how light on features the import command is. I was about to switch my bespoke winget scripts over to use import instead of install, but instantly ran into some dealbreakers.
Notably, some of the packages I'm installing require the use of --custom, and I wish that I could also specify silent per-package.

I imagine some people would require --location and --architecture, and --override to genuinely make use of this feature as well. I can't imagine many people are using import given the current state?

Note this is distinctly different than #3373 which I believe is wanting more functionality at the command level, rather than the per-package level.

Proposed technical implementation details

I haven't dug into winget-cli's code but I'm hopeful it isn't too difficult to add additional optional entries to packages.schema.2.0.json, for each of these features much the same way that Scope is in there.

Then from there, assuming import calls into the same path as winget install does, just construct the arguments from the imported json as necessary.

There is an open question on exporting some of these things given that the history of them may have been lost after install?

Start with schemas/JSON/packages/packages.schema.2.0.json, then trace how import invokes the install path and where per-package options are constructed. Done means the package schema and import processing cover the requested per-package options, with export behavior addressed as part of the open question.