[FEATURE REQUEST] Socket Firewall integration for package installations

### Please confirm these before moving forward.

- [x] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [x] This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=enhancement&projects=&template=enhancement-improvement.yml&title=%5BENHANCEMENT%5D+%28Enter+your+description+here%29).

### Describe the new feature

Add an optional Socket Firewall (sfw) toggle for supported package managers. When enabled, UniGetUI would run package operations through SFW, e.g. `sfw npm install`, `sfw pip install`, and `sfw cargo ...`. It is particularly useful for reducing supply-chain risk by checking packages before they are fetched and installed.

Native handling is needed because Pip currently runs as `python -m pip`, which cannot be protected by simply selecting `sfw.exe` as its executable.

### Describe how this new feature could help users

This would provide install-time protection against malicious dependencies directly in UniGetUI, without requiring PATH shims, custom wrappers, or manual terminal commands.

No files, tests, or code entry points are named. Start by tracing how UniGetUI constructs package-manager operations for npm, pip, and cargo, then determine how an optional Socket Firewall toggle would apply to each, including pip's python -m pip invocation. Done means supported managers can run through SFW without PATH shims or manual commands.

Written by the indexing model from the issue text.