fix: drop the "Reserved for 3GPP" event-name cross-reference (v3.6.22)

The event list tables carried labels like
"12  Reserved for 3GPP - Network rejection (TS 31.111 7.5.2)".  The phrase is
an ETSI-to-3GPP document pointer, not a usage restriction, and it is not
what a user needs - the event name is.

- EVENT_NAMES (PWA + server mirror): the 3GPP-assigned codings carry their
  plain TS 31.111 7.5 name ((I-)WLAN access status, Network rejection, CSG
  cell selection, IMS registration, Incoming IMS data, Data connection
  status change, CAG cell selection, Slices status change).
- 0x20-0x22: "Reserved (future usage)" (no attribution).
- 0x0B/0x14: the spec's full "(single access technology)" / "(multiple
  access technologies)" wording instead of the cryptic "(single)/(multiple)".
- tests pin the exact names and that no name contains the cross-reference.

652 frontend / 500 Python green; version 3.6.22; sw simple-v295.

pysim_simple_server/server.py

@@ -31,7 +31,7 @@ from osmocom.tlv import BER_TLV_IE
 from osmocom.utils import rpad
 
 
-VERSION = '3.6.21'
+VERSION = '3.6.22'
 
 MAX_ENVELOPE_SEGMENTS = 5  # max SMS segments for outgoing C-APDU in ENVELOPE
 
@@ -1769,34 +1769,35 @@ def _tr_data_only(tr_tlv):
     return bytes(data)
 
 
-# Event list codings (TS 102 223 v18.3.0 8.25).  Values the CAT spec leaves
-# "Reserved for 3GPP" carry the concrete 3GPP event name where TS 31.111
-# defines one (clauses in parentheses), so the list stays informative.
+# Event list codings (TS 102 223 v18.3.0 8.25).  The values the CAT spec only
+# points at 3GPP for carry their TS 31.111 7.5 event name; "Reserved for
+# 3GPP" is a spec cross-reference, not a usage restriction, so it never
+# appears in the user-facing names.
 EVENT_NAMES = {
     0x00: 'MT call', 0x01: 'Call connected', 0x02: 'Call disconnected',
     0x03: 'Location status', 0x04: 'User activity', 0x05: 'Idle screen available',
     0x06: 'Card reader status', 0x07: 'Language selection',
     0x08: 'Browser termination', 0x09: 'Data available',
-    0x0A: 'Channel status', 0x0B: 'Access technology change (single)',
+    0x0A: 'Channel status', 0x0B: 'Access technology change (single access technology)',
     0x0C: 'Display parameters changed', 0x0D: 'Local connection',
     0x0E: 'Network search mode change', 0x0F: 'Browsing status',
     0x10: 'Frames information change',
-    0x11: 'Reserved for 3GPP \u2014 (I-)WLAN access status (TS 31.111 7.5.1)',
-    0x12: 'Reserved for 3GPP \u2014 Network rejection (TS 31.111 7.5.2)',
+    0x11: '(I-)WLAN access status',
+    0x12: 'Network rejection',
     0x13: 'HCI connectivity',
-    0x14: 'Access technology change (multiple)',
-    0x15: 'Reserved for 3GPP \u2014 CSG cell selection (TS 31.111 7.5.3)',
+    0x14: 'Access technology change (multiple access technologies)',
+    0x15: 'CSG cell selection',
     0x16: 'Contactless state request',
-    0x17: 'Reserved for 3GPP \u2014 IMS registration (TS 31.111 7.5.21)',
-    0x18: 'Reserved for 3GPP \u2014 Incoming IMS data (TS 31.111 7.5.20)',
+    0x17: 'IMS registration',
+    0x18: 'Incoming IMS data',
     0x19: 'Profile container', 0x1A: 'Void', 0x1B: 'Secured profile container',
     0x1C: 'Poll interval negotiation',
-    0x1D: 'Reserved for 3GPP \u2014 Data connection status change (TS 31.111 7.5.25)',
-    0x1E: 'Reserved for 3GPP \u2014 CAG cell selection (TS 31.111 7.5.26)',
-    0x1F: 'Reserved for 3GPP \u2014 Slices status change (TS 31.111 7.5.27)',
-    0x20: 'Reserved for 3GPP (future usage)',
-    0x21: 'Reserved for 3GPP (future usage)',
-    0x22: 'Reserved for 3GPP (future usage)',
+    0x1D: 'Data connection status change',
+    0x1E: 'CAG cell selection',
+    0x1F: 'Slices status change',
+    0x20: 'Reserved (future usage)',
+    0x21: 'Reserved (future usage)',
+    0x22: 'Reserved (future usage)',
 }
 
 ACCESSTECH_NAMES = {