Convert repository into an OxideBot app template

[canxin121]

What changed

• Reframes the repository as a GitHub template for building custom OxideBot Android Root applications.
• Replaces the personal China Unicom runner with a minimal Telegram /start and /echo example.
• Adds template.properties as the single source for module ID, app identity, version, required environment variables, and repository metadata.
• Generates module.prop, update.json, module paths, WebUI paths, APK package identity, and release filenames from template configuration.
• Keeps four-ABI Android builds, Root module WebUI, the Android manager, and signed tag releases.
• Adds template rendering tests and documentation for creating and releasing a user-owned application.

Why

OxideBot is a framework rather than a ready-to-use bot. Each user must select adapters, write handlers, and compile their own application. The repository should therefore distribute a reusable build/deployment template, not one author-specific runtime.

User impact

After creating a repository with Use this template, users edit template.properties and runner/, push to main for test artifacts, then push a matching v* tag for a signed module/App release. Different template projects get distinct module IDs, APK application IDs, data directories, and update URLs.

Validation

• cargo check --locked for the minimal example
• real Android arm64 cross-build with NDK 29
• controller lifecycle tests
• template rendering and update URL tests
• WebUI JavaScript syntax check
• Android Debug build with dynamic application identity
• signed Android Release build and APK v2 signature verification
• shell/YAML syntax and whitespace checks