Add comprehensive repository documentation with bilingual README

[Copilot]

Repository lacked structured documentation for the sample collection. Added comprehensive README files in English and Chinese covering the GeneralUpdate automatic update framework samples.

Changes

• README.md / README_zh.md: Complete documentation structure
  • Repository layout with 8 sample projects (Client, Server, Upgrade, OSS, Bowl, Diff, Push, Compress, Drivelution, Extension)
  • Quick start for standard and OSS update mechanisms
  • Code examples for each sample type with configuration patterns
  • UI framework integration samples (AntdUI, LayUI, SemiUrsa, WPF)
  • Ecosystem links (GeneralUpdate, GeneralUpdate.Maui, GeneralUpdate.Tools)
  • Environment requirements (.NET 8.0, cross-platform OS support)

Documentation Coverage

Standard Update Flow:

var configinfo = new Configinfo
{
    UpdateUrl = "http://127.0.0.1:5000/Upgrade/Verification",
    ClientVersion = "1.0.0.0",
    ProductId = "2d974e2a-31e6-4887-9bb1-b4689e98c77a"
};

await new GeneralClientBootstrap()
    .AddListenerMultiDownloadStatistics(OnMultiDownloadStatistics)
    .SetConfig(configinfo)
    .LaunchAsync();

OSS Update (Simplified):
Uses version.json on file server instead of server-side code - documented for developers choosing between update mechanisms.

Each sample project documented with purpose, key features, and integration patterns. Website build instructions included for Docusaurus documentation site.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Repository README Writing</issue_title>
<issue_description>Based on all files, code, and modules in the current repository, analyze the overall logic and core functions of the project, and write a README.md file with a standardized structure and complete content, including essential sections such as project overview, introduction to core functions, quick start guide, and explanation of directory structure.</issue_description>

<agent_instructions>请充分理解issue、仓库所有内容上下文。</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Repository README Writing #33

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Pull request overview

This pull request adds comprehensive bilingual README documentation (English and Chinese) to the GeneralUpdate-Samples repository, replacing the minimal previous README. The documentation provides a complete guide to the repository's structure, purpose, and usage.

Changes:

• Added detailed bilingual README files (README.md and README_zh.md) with complete project documentation
• Documented 10 sample projects covering standard updates, OSS updates, differential updates, process monitoring, push notifications, compression, driver updates, and extensions
• Included quick start guides, code examples, environment requirements, and contribution guidelines

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
README.md	Comprehensive English documentation including project overview, features, repository structure, quick start guides, sample project descriptions, UI framework examples, related repositories, requirements, and support information
README_zh.md	Chinese translation of the complete documentation, mirroring the English version's structure and content

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The documentation refers to "version.json" but the actual implementation uses "versions.json" (plural). This should be updated to match the actual filename used in the codebase.

Suggested change

	- 使用文件服务器上的 `version.json` 配置
	- 直接集成文件服务器（阿里云 OSS、AWS S3 等）
	- 支持 AOT 编译
	**version.json 示例：**
	- 使用文件服务器上的 `versions.json` 配置
	- 直接集成文件服务器（阿里云 OSS、AWS S3 等）
	- 支持 AOT 编译
	**versions.json 示例：**

[Copilot]

The PR description states "Repository layout with 8 sample projects" but the documentation correctly lists 10 distinct sample projects: Client, Server, Upgrade, OSS (which contains 2 sub-samples), Bowl, Diff, Push, Compress, Drivelution, and Extension. The PR description should be updated to reflect the actual count of 10 sample projects, or if counting top-level directories only, it should be 9 (since OSS is one directory containing two samples).

[Copilot]

The documentation refers to "version.json" but the actual implementation uses "versions.json" (plural). This is evident in the Server code at src/Server/wwwroot/packages/versions.json and the OSS client code at src/OSS/OSSClientSample/Program.cs line 9. The documentation should be updated to use the correct filename "versions.json" throughout.

Suggested change

	This demonstrates OSS-based updates using only a `version.json` configuration file on a file server.
	This demonstrates OSS-based updates using only a `versions.json` configuration file on a file server.

[Copilot]

The documentation refers to "version.json" but the actual implementation uses "versions.json" (plural). This should be updated to match the actual filename used in the codebase.

Suggested change

	- Uses `version.json` configuration on file server
	- Direct file server integration (Alibaba Cloud OSS, AWS S3, etc.)
	- Supports AOT compilation
	**version.json Example:**
	- Uses `versions.json` configuration on file server
	- Direct file server integration (Alibaba Cloud OSS, AWS S3, etc.)
	- Supports AOT compilation
	**versions.json Example:**

[Copilot]

The documentation refers to "version.json" but the actual implementation uses "versions.json" (plural). This should be updated to match the actual filename used in the codebase.

Suggested change

	这演示了基于 OSS 的更新，仅使用文件服务器上的 `version.json` 配置文件。
	这演示了基于 OSS 的更新，仅使用文件服务器上的 `versions.json` 配置文件。