docs: rebrand the repository documentation, templates and dashboards

README, README_ZH, SECURITY, COMPLIANCE, CONTRIBUTING, NOTICE,
code_of_conduct, the vulnerability and PR-etiquette documents, the GitHub issue
and pull request templates, and the docs/ tree all present Silo as the product.
The Grafana dashboards under docs/metrics/prometheus/grafana/ have their panel
titles and descriptions rebranded while every minio_* query, label and
expression is left alone, so existing alerts and recording rules keep matching.

The distinction the review demanded is applied per hit rather than by
search-and-replace:

- Product and command text becomes Silo and silo: install and run instructions,
  systemd examples, compose services, download links, badges.
- Protocol and interface text keeps MinIO: MINIO_* variables, minio_* metrics,
  x-minio-* headers, /minio/* routes, .minio.sys, arn:minio, and API field and
  error names.
- Attribution keeps MinIO and gains the fork's own: the AGPL obligations,
  original copyright, CREDITS and NOTICE stay, with the modification notice
  added alongside rather than replacing them.
- Historical and third-party references are left as facts, not rewritten for
  brand tidiness.

README and README_ZH each carry an explicit non-affiliation notice, document
the side-by-side package migration including the
/etc/systemd/system/silo.service.d/10-legacy-user.conf drop-in for keeping a
legacy UID/GID, and state that recursive chown is never performed. The trademark
attribution uses the policy's approved "based on MinIO technology" wording, not
the shortened form the policy rejects.

github.com/pgsty/minio links are left in place and labelled transitional. The
repository has not been renamed, and rewriting them now would produce documented
URLs that 404 until the cutover; they change in the cutover commit together with
the goreleaser release target, the OCI source label and the raw-content branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/ftp/README.md

@@ -1,6 +1,6 @@
-# MinIO FTP/SFTP Server
+# Silo FTP/SFTP Server
 
-MinIO natively supports FTP/SFTP protocol, this allows any ftp/sftp client to upload and download files.
+Silo natively supports FTP/SFTP protocol, this allows any ftp/sftp client to upload and download files.
 
 Currently supported `FTP/SFTP` operations are as follows:
 
@@ -15,7 +15,7 @@ Currently supported `FTP/SFTP` operations are as follows:
 | append              | no        |
 | rename              | no        |
 
-MinIO supports following FTP/SFTP based protocols to access and manage data.
+Silo supports following FTP/SFTP based protocols to access and manage data.
 
 - Secure File Transfer Protocol (SFTP) – Defined by the Internet Engineering Task Force (IETF) as an
   extended version of SSH 2.0, allowing file transfer over SSH and for use with Transport Layer
@@ -41,7 +41,8 @@ MinIO supports following FTP/SFTP based protocols to access and manage data.
   - OpenID/OIDC service accounts
 
 - On versioned buckets, FTP/SFTP only operates on latest objects, if you need to retrieve
-  an older version you must use an `S3 API client` such as [`mc`](https://github.com/minio/mc).
+  an older version you must use an S3 API client such as the compatible
+  [`mc`](https://github.com/pgsty/mc) client.
 
 - All features currently used by your buckets will work as is without any changes
   - SSE (Server Side Encryption)
@@ -58,10 +59,10 @@ MinIO supports following FTP/SFTP based protocols to access and manage data.
 
 ## Usage
 
-Start MinIO in a distributed setup, with 'ftp/sftp' enabled.
+Start Silo in a distributed setup, with 'ftp/sftp' enabled.
 
 ```
-minio server http://server{1...4}/disk{1...4}
+silo server http://server{1...4}/disk{1...4}
    --ftp="address=:8021" --ftp="passive-port-range=30000-40000" \
    --sftp="address=:8022" --sftp="ssh-private-key=/home/miniouser/.ssh/id_rsa"
 ...
@@ -73,7 +74,7 @@ Following example shows connecting via ftp client using `minioadmin` credentials
 ```
 ftp localhost -P 8021
 Connected to localhost.
-220 Welcome to MinIO FTP Server
+220 Welcome to Silo FTP Server
 Name (localhost:user): minioadmin
 331 User name ok, password required
 Password:
@@ -163,7 +164,7 @@ Unlike SFTP server, FTP server is insecure by default. To operate under TLS mode
 --ftp="tls-private-key=path/to/private.key" --ftp="tls-public-cert=path/to/public.crt"
 ```
 
-> NOTE: if MinIO distributed setup is already configured to run under TLS, FTP will automatically use the relevant
+> NOTE: if Silo distributed setup is already configured to run under TLS, FTP will automatically use the relevant
 > certs from the server certificate chain, this is mainly to add simplicity of setup. However if you wish to terminate
 > TLS certificates via a different domain for your FTP servers you may choose the above command line options.