Single file publishing documentation makes no mention of compression memory overhead

### Describe the issue or suggestion

https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?source=recommendations&tabs=cli#compress-assemblies-in-single-file-apps

I was absolutely shocked to discover that a single-file app I was using had a **350 MB** private working set segment purely for decompressed R2R code. While the documentation does say there is a "startup overhead", this feels like an outrageous amount of difference that app developers might not be aware of.

I have not done measurements on this, but it does not seem unreasonable to guess that **all** the point of R2R is basically thrown away entirely by this system. Especially if users have slower disks or higher memory pressure.

---
#### Document Details

⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.*

* ID: e1932751-7c2b-ce92-936e-e97f8581d5fa
* Version Independent ID: de677d1f-386a-e4c3-fdd0-6806b3ef2c0e
* Platform ID: 2f1a1ee6-f476-0835-409f-2cc17a9c022d
* Content: [Create a single file for application deployment - .NET](https://learn.microsoft.com/en-us/dotnet/core/deploying/single-file/overview?source=recommendations&tabs=cli#compress-assemblies-in-single-file-apps)
* Content Source: [docs/core/deploying/single-file/overview.md](https://github.com/dotnet/docs/blob/main/docs/core/deploying/single-file/overview.md)
* Service: **dotnet-fundamentals**
* GitHub Login: @LakshanF
* Microsoft Alias: **adegeo**