Support for filtering packages on installer method

Description

Some installers do not support a silent/unattended experience. WinGet should let users express a requirement or a preference for install modes (e.g., silent vs. interactive), configurable in settings and via command-line arguments, and honor it consistently across search, install, and import.

Behavior

Search

• When a user requires silent, search results should omit packages whose manifests can't satisfy silent install.
• Allow filtering results to include/exclude interactive-only packages.

Install

• Honor the user's preferred install mode when the package supports it.
• If the user requires a mode and it can't be respected for a package, inform the user rather than silently falling back.

Import

• Respect the user's install-mode preferences when importing a set of packages.
• If a required mode can't be respected for one or more packages, inform the user.

Notes

• Should support both a preference (best-effort) and a hard requirement.
• This capability is a prerequisite to allowing packages with only an interactive install mode into the community repository.

Consolidates #910.

Start by tracing how settings and command-line arguments reach the search, install, and import entry points. Define how preference versus requirement affects silent and interactive install modes, including unsupported packages. Done means all three flows consistently honor preferences and clearly report when a required mode cannot be respected.