ZipArchive documentation still mentions 2GB limit in Update mode

### Type of issue

Outdated article

### Description

Many of the ZipArchive related pages mention the 2GB limit when Mode is set to Update.
I believe this has been resolved in .NET 10 and should be removed from all documentation.

As shown in the release notes below:

> the way entries are written to a ZipArchive when in Update mode has been optimized. Previously, all ZipArchiveEntry instances were loaded into memory and rewritten,

[.NET 10 Release Notes - Zip Performance](https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/preview1/libraries.md#ziparchive-performance-and-memory-improvements)

### Page URL

https://learn.microsoft.com/en-us/dotnet/api/system.io.compression.zipfileextensions.createentryfromfile?view=net-10.0#system-io-compression-zipfileextensions-createentryfromfile(system-io-compression-ziparchive-system-string-system-string-system-io-compression-compressionlevel)

### Content source URL

https://github.com/dotnet/dotnet-api-docs/blob/main/xml/System.IO.Compression/ZipFileExtensions.xml

### Document Version Independent Id

e4676cb1-22e3-0197-d0fc-2486a311fcc7

### Platform Id

492a107d-eaa4-fcf8-3475-11feb18f68ca

### Article author

@dotnet-bot

Start with xml/System.IO.Compression/ZipFileExtensions.xml and review the linked .NET 10 Zip Performance release notes. Search the API documentation for other ZipArchive pages mentioning the 2GB Update-mode limit, then verify that all outdated references are removed while the remaining guidance is accurate.

Written by the indexing model from the issue text.