Store branding images as base64 and embed in READMEs

[AkarinServer]

Motivation

• Avoid storing binary PNGs in the repo and retain branding visuals in documentation by storing images as base64 text assets and embedding them in READMEs.
• Ensure READMEs (English/中文 and per-component) continue to show the lockup and per-app icons without binary files.

Description

• Replaced PNG branding files with base64 text files: assets/branding/secgo-lockup.base64, Kiosk/assets/branding/secgo-kiosk-icon.base64, Manager/assets/branding/secgo-manager-icon.base64, and Server/assets/branding/secgo-server-icon.base64.
• Updated README renderings to inline data URIs using the base64 content for the horizontal lockup and each component icon in README.md, README_zh.md, Kiosk/README.md, Manager/README.md, and Server/README.md.
• Removed the original binary .png assets and replaced their Markdown image references with <img alt=... src="data:image/png;base64,..." /> embeddings that reference the created .base64 files.
• Kept bilingual navigation and existing README content; changes are documentation/assets-only and do not modify runtime code.

Testing

• No automated tests were run because this is a documentation/assets-only change.
• Repo state was updated and files staged for review; normal CI (lint/test workflows) will run on pushes/PRs as configured.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 717f3a567a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid data URI images that GitHub strips from README

GitHub’s README renderer sanitizes HTML and generally strips data: URLs from <img> tags for security reasons, so this inline base64 image won’t display on GitHub (and many other Markdown viewers). That defeats the commit’s stated goal of keeping the branding visuals visible in the README; users browsing the repo will see no image. Consider keeping a normal image file in the repo (or hosting the asset) and referencing it via a standard src URL instead.

Useful? React with 👍 / 👎.