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/admin/wechat-settings-rest-contract.test.cjs

@@ -6,8 +6,8 @@
  * 2) 状态读取委托 WeChatNotify::get_status()，写入委托 Settings::update_wechat_settings()；
  * 3) app_secret 掩码 *** 不覆盖已存密钥，输入经 sanitize_text_field 消毒；
  * 4) PHP harness 驱动真实控制器验证上述行为；
- * 5) aksrt_settings 上的微信通知死键（wechat_notify_* 等）已彻底移除，
- *    活配置面仅剩 aksrt_wechat_settings（/users/wechat-template 自定义页）。
+ * 5) jio_settings 上的微信通知死键（wechat_notify_* 等）已彻底移除，
+ *    活配置面仅剩 jio_wechat_settings（/users/wechat-template 自定义页）。
  */
 
 const assert = require('node:assert/strict');
@@ -22,7 +22,7 @@ const schemaUsers = fs.readFileSync(path.join(root, 'src/Admin/Schema/SchemaUser
 const usersSchemaIndex = fs.readFileSync(path.join(root, 'assets/admin/src/schema/sections/users/index.js'), 'utf8');
 const usersSections = fs.readFileSync(path.join(root, 'assets/admin/src/constants/sections/users.js'), 'utf8');
 
-// 死双路面：写进 aksrt_settings、全仓无消费方的微信通知键。
+// 死双路面：写进 jio_settings、全仓无消费方的微信通知键。
 const DEAD_WECHAT_KEYS = [
   'wechat_notify_enabled',
   'wechat_app_id',
@@ -66,7 +66,7 @@ test('微信设置行为 harness 通过', () => {
   assert.match(output, /WeChat settings harness passed/);
 });
 
-test('死双路面（aksrt_settings 微信通知键）已彻底移除', () => {
+test('死双路面（jio_settings 微信通知键）已彻底移除', () => {
   for (const key of DEAD_WECHAT_KEYS) {
     assert.ok(!schemaUsers.includes(key), `SchemaUsers 残留: ${key}`);
     assert.ok(!usersSections.includes(key), `users 菜单常量残留: ${key}`);
@@ -76,7 +76,7 @@ test('死双路面（aksrt_settings 微信通知键）已彻底移除', () => {
   assert.ok(!fs.existsSync(path.join(root, 'assets/admin/src/schema/sections/users/wechat.js')), 'wechat.js 未删除');
 });
 
-test('活配置面保持唯一（aksrt_wechat_settings + 自定义页）', () => {
+test('活配置面保持唯一（jio_wechat_settings + 自定义页）', () => {
   assert.match(usersSections, /key: 'users-wechat-template'/);
   assert.match(usersSections, /route: '\/users\/wechat-template'/);
   assert.match(controller, /WeChatNotify::get_instance\(\)->get_status\(\)/);