refactor: rename the theme brand and every identifier from AKSRT to Jio

Full-project rename. `git grep -i aksrt` is now empty apart from the
DBMigrator 3.3.0 changelog note that documents the rename itself.

Code identifiers
- PHP namespace AKSRT\ -> Jio\ (composer PSR-4 + 378 declarations)
- global constants AKSRT_* -> JIO_* (VERSION/DIR/URI, PAY_TYPE_*, CAPTCHA_*)
- procedural functions, hooks, options, meta keys, table names,
  cookies, query vars, ajax actions and nonces: aksrt_ -> jio_
- text domain aksrt -> jio; Theme Name -> Jio
- JS globals: aksrtData/aksrtAdminData/... -> jioData/jioAdminData/...,
  window.AKSRTCaptcha & friends -> window.JioCaptcha, Aksrt* -> Jio*
- Vue components Aks*.vue -> Jio*.vue (15 files renamed + imports)
- CSS classes/data-attrs/custom properties: aksrt- -> jio-
- REST namespace aksrt/v1 -> jio/v1 (incl. payment gateway callbacks)

Storage layer
- DB tables {prefix}aksrt_* -> {prefix}jio_*; SCHEMA_VERSION 3.2.0 -> 3.3.0
  so dbDelta creates the new names on install
- widget id_base aksrt_widget_* -> jio_widget_*
- uninstall.php drop list rebuilt from the actual migrator tables
  (dropped 3 stale entries, added the 17 missing ones)

Removed
- hardcoded https://api.aksrt.com/version.json default update endpoint;
  get_endpoint() now reads the 「更新端点」 setting and do_check() no-ops
  when it is empty

Files renamed: inc/helpers/aksrt-*.php -> jio-*.php (54),
assets/admin/src/components/form/Aks*.vue -> Jio*.vue (15).
Build artifacts regenerated: assets/css/build, assets/js/runtime,
assets/admin/build.

Verified: audit-psr4-paths errors=0, audit-admin-contracts errors=0
(warnings=56, unchanged baseline), 813/813 widget-system tests,
44/44 phpunit, php -l clean across all PHP.

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

tests/visual/README.md

@@ -1,17 +1,17 @@
-# AKSRT / Zibll visual reference
+# Jio / Zibll visual reference
 
-The reference stack is isolated from the AKSRT site and exposes Zibll at
+The reference stack is isolated from the Jio site and exposes Zibll at
 https://localhost:9443. The local Zibll source remains read-only.
 
 ~~~powershell
 $env:ZIBLL_THEME_PATH='C:\Users\Xing\Desktop\zibll'
 docker compose -f tests/visual/docker-compose.zibll.yml up -d
-docker compose -f tests/visual/docker-compose.zibll.yml run --rm wp core install --url=https://localhost:9443 --title='Zibll Reference' --admin_user=visual_admin --admin_password='AKSRT-Visual-2026!' --admin_email=visual@example.test --skip-email
+docker compose -f tests/visual/docker-compose.zibll.yml run --rm wp core install --url=https://localhost:9443 --title='Zibll Reference' --admin_user=visual_admin --admin_password='Jio-Visual-2026!' --admin_email=visual@example.test --skip-email
 docker compose -f tests/visual/docker-compose.zibll.yml run --rm wp theme activate zibll
 docker compose -f tests/visual/docker-compose.zibll.yml run --rm wp eval-file /visual-fixtures/article-fixtures.php create
 ~~~
 
-Run the same theme-neutral article generator inside the AKSRT WordPress
+Run the same theme-neutral article generator inside the Jio WordPress
 container. Mount `tests/visual/` read-only at `/visual-fixtures` in that stack:
 
 ~~~powershell
@@ -22,7 +22,7 @@ wp eval-file /visual-fixtures/article-fixtures.php cleanup
 The shared generator creates the same authors, category, tag, dates, images,
 featured/no-image/multi-image/first-image/external-cover posts, slide and video
 metadata, pay/VIP states, sticky state, and interaction counters in both sites.
-Fixture-only Zibll and AKSRT metadata are written together so the rendered
+Fixture-only Zibll and Jio metadata are written together so the rendered
 business state is identical without adding compatibility code to either theme.
 
 Use `tests/visual/article-visual-matrix-v1.json` for the article-only captures.