fix(mapping): correct region↔IO mapping per on-device measurement

Measured on real hardware: IO1=right IO2=left IO3=top IO4=middle IO5=bottom
(0x01=right 0x02=left 0x04=top 0x08=middle 0x10=bottom). The earlier verbal
'left=IO1/upper=IO2...' spec was wrong; this reverts to the original Phase-1
mapping, which the measurement confirms.

- protocol.js REGION constants + getRegionName + REGION_NAMES
- CRITICAL: buildVendorCommand ioMasks was built from REGION.* constants whose
  values just flipped, scrambling IO slot order; pin to literal [0x01..0x10]
- diagnosis.js REGION_DEFS key↔mask; pd_region_map values unchanged (PD is
  keyed by orientation, which is stable) — right=PD5 left=PD1 top=PD2
  middle=PD3,6,7 bottom=PD4
- common.js region labels back to right/left/top/middle/bottom (上/中/下)
- treatment-setup / manual-treatment / treating / scan-report / ble-debug
  face-map bindings and REGION_MAP realigned
- verified: mock pipeline lands left→IO2, middle→IO4 correctly

miniprogram/pages/treatment-setup/treatment-setup.js

@@ -34,8 +34,8 @@ Page({
     var app = getApp()
     this.setData({ statusBarHeight: app.globalData.statusBarHeight })
     i18n.bind(this)
-    // 顺序对应 data.regions 的掩码 0x01..0x10（IO1..IO5 = 左/中上/中/中下/右）
-    var regionKeys = ['left', 'top', 'middle', 'bottom', 'right']
+    // 顺序对应 data.regions 掩码 0x01..0x10 = IO1..IO5 = 右/左/上/中/下（实测）
+    var regionKeys = ['right', 'left', 'top', 'middle', 'bottom']
     var regions = this.data.regions
     regions.forEach(function (r, i) {
       r.name = i18n.t('common.regions.' + regionKeys[i])