Compress runtime/modules to reduce deployment package unzipped size

AWS Lambda limits ZIP deployment packages to 250 MB on-disk. The Linux PowerShell release builds are ~170 MB in the current release, which takes up ~70% of that cap. (Community members' attempts at producing "slim" PowerShell containers only reduce sizes by ~30MB, which isn't a ton in broader context.)

Pure PowerShell script modules are generally quite small, but compiled CLR module assemblies or autogenerated modules (e.g. `Microsoft.Graph.*`, `Az.*`, `AWS.Tools.*`) can get very large.

The current architecture only allows for ~80MB of module dependencies - `AWS.Tools.S3` and `Microsoft.Graph.Users` (with respective dependencies) breaches the 250MB cap.

Compressing the PowerShell runtime itself would:
* Free up >100MB of deployment package size (172MB vs 66 MB)
* Unblock build artifact verification (PowerShell publishes SHAs of release artifacts)

Supporting compressed module dependencies (e.g. `/opt/modules-packed.zip` or `/opt/modules-packed/*.nupkg` gets unpacked to `/tmp/modules-unpacked` and added to PSModulePath) could help the situation as well.

Commencez par examiner le packaging de release de Linux PowerShell et la manière dont les dépendances des modules sont incluses dans le deployment ZIP. Comparez l’artefact actuel de 172 MB avec le runtime compressé ou les modules empaquetés proposés, et prenez en compte les chemins /opt et /tmp d’AWS Lambda mentionnés. C’est terminé lorsque l’artefact de release est nettement plus petit, que les dépendances des modules restent disponibles et que la vérification de l’artefact n’est plus bloquée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.