Add ceedump lang

[1000TurquoisePogs]

Proposed changes

This PR adds a CEEDUMP language mode.

Changes:

• webClient/src/app/editor/code-editor/monaco/hiliters/ceedump.ts — new file containing:
  • CEEDUMP_HILITE: Monarch tokenizer covering page banners, section/sub-section headers, register name labels, CEE message identifiers, memory storage hex dumps (with per-byte group highlighting for 32-bit and 64-bit addresses), EBCDIC decoded character columns, compile attributes, traceback status keywords, and inaccessible storage markers.
  • CEE_MESSAGES: Descriptions for some CEE message IDs
  • CEEDUMP_HOVER_DOCS: Hover tooltip content for section headers, linkage terms (DSA, CIB, PSW, ILC, BKC, FWC, NAB, PNAB, UPSTACK DSA, XPLINK DSA), and other CEEDUMP vocabulary.
• webClient/src/app/editor/code-editor/monaco/monaco.config.ts — registers the ceedump language with filenamePatterns: ['^CEEDUMP\\.'] for automatic detection, applies the Monarch tokenizer, registers the hover provider (including per-GPR descriptions for GPR0–15, and FPR/VR entries), and defines the ceedump-dark theme.

Type of change

• New feature (non-breaking change which adds functionality)

PR Checklist

• If the changes in this PR are meant for the next release / mainline, this PR targets the "staging" branch.
• My code follows the style guidelines of this project (see: Contributing guideline)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes
• video or image is included if visual changes are made
• Relevant update to CHANGELOG.md
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works, or describe a test method below

Testing

1. Build the editor plugin and deploy to a Zowe Desktop instance.
2. Open a CEEDUMP file (e.g. CEEDUMP.20260401.072907.131080) via the File Explorer or by path. The editor should automatically select the CEEDUMP language mode.
3. Verify syntax highlighting:
   • Page banners (CEE3DMP V3 R2.0: …) appear in yellow bold.
   • Section headers (Traceback:, Information for enclave …, etc.) appear in green.
   • CEE message IDs (CEE3845I, CEE3204S, etc.) appear in orange.
   • Register labels (GPR0....., FPR0....., VR0......) appear in cyan bold.
   • 32-bit hex values have their first byte in cyan and lower 3 bytes in dark cyan.
   • 64-bit hex values (XXXXXXXX_YYYYYYYY) have the high byte in bright green, high word in medium green, middle byte in cyan, and lower 3 bytes in dark cyan.
   • ******** inaccessible address markers appear in red.
   • EBCDIC decoded columns between |…| appear in gray italic.
4. Hover over:
   • A CEE message ID to see the diagnostic description.
   • A section header keyword (Traceback, DSA, CIB, PSW, ILC, NAB, etc.) to see the hover tooltip.
   • A register label (GPR13, FPR0, VR0) to see the register role description.
5. Manually switch the language mode to CEEDUMP from the language picker and confirm it is listed as CEEDUMP.

[timgerstel]

I believe ceedump.ts contains em dashes as well.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud