Fix 30 KB errors: ExaCS storage 3-10x wrong, ECPU transition, IOPS limits, missing shapes

Cross-referenced all 70+ KB files against official Oracle docs. Critical fixes:
- ExaCS: storage was flash cache not usable disk (76.8→190.8 TB QR), added X11M, removed X10M
- ADB-S: OCPU→ECPU migration, 26ai as default, cross-region RTO 15→10 min
- Compute: E5 max 94→126, A2 80→78, added E6/A4/BM shapes, 11 GPU shapes
- Storage: Higher Perf IOPS 35K→50K, UHP 450K→300K, File Storage 25K→50K
- DBCS: E5.Flex max 94→64, storage 80→150 TB, added 26ai
- Networking: FastConnect +400 Gbps, NSG max 120 rules

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

kb/sizing/storage-iops.yaml

@@ -21,18 +21,19 @@ block_volume:
 
     - name: "Higher Performance"
       iops_per_gb: 75
-      max_iops: 35000
+      max_iops: 50000
       throughput_mbps_per_gb: 0.6
-      max_throughput_mbps: 480
+      max_throughput_mbps: 680
       use_when: "Database data files, high-throughput applications"
 
     - name: "Ultra High Performance"
       iops_per_gb: 90
-      max_iops: 120000
+      max_iops: 300000
+      iops_range: "75,000 - 300,000 (at 30-120 VPU)"
       throughput_mbps_per_gb: 0.72
       max_throughput_mbps: 2680
       use_when: "Extreme IOPS requirements, OLTP databases"
-      notes: "Only available with certain compute shapes"
+      notes: "Only available with certain compute shapes. IOPS scales with VPU (30-120)."
 
   sizing_guidance: |
     1. Determine required IOPS (from AWR, CloudWatch, or application benchmarks)