feat: add highlight action-request that forwards ids to NMRium's highlightedIds

[vcnainala]

Summary

• Adds host-driven highlighting on the nmr-wrapper:action-request channel using NMRium's highlightedIds prop (feat: support externally controlled highlights cheminfo/nmrium#4405, released in NMRium 3.1).
• New actions:
  • highlight with params: { ids: string[] }: passes the ids to highlightedIds and replaces the previous host highlight.
  • clearHighlight: clears the host highlight.
• The wrapper does not store NMRium's state or look anything up. The host finds the peak, range and signal ids in its own data and sends them. NMRium keeps the ids it is given in the loaded data, so ids from the host's payload match.
• To highlight on another nucleus, the host sends selectTab and then highlight.
• highlightedIds is additive: NMRium's own hover/click highlighting keeps working, and Delete/Backspace cannot remove a host-highlighted peak or range.
• Invalid params.ids and unknown action types emit nmr-wrapper:error instead of throwing.
• Demo: Test load QM signals, Test highlight signal and Clear highlight buttons, using a fixture generated by qm-nmr-calc's payload builder.

Example:

iframe.postMessage(
  {
    type: 'nmr-wrapper:action-request',
    data: {
      type: 'highlight',
      params: { ids: ['qm-signal-1H-7-8', 'qm-range-1H-7-8', 'qm-1H-7-8'] },
    },
  },
  origin,
);

Rebased on development (NMRium 3.1, React 19).

Test plan

• npm run check-types, eslint, prettier
• npx playwright test --project chromium: all 11 pass, including highlight a peak by id, highlight a signal with its range and peak, selectTab followed by highlight on another nucleus, and invalid ids emitting nmr-wrapper:error
• Demo: Test load QM signals, then Test highlight signal highlights the 3.69 ppm range and peak; Clear highlight clears it

[hamed-musallam]

@vcnainala

I’ve taken a look at the code, and I’m not convinced that saving the last NMRium state in the wrapper is the right approach. All the logic for finding peak IDs or range IDs should be handled entirely on your side and should not be part of the RW. The wrapper’s only responsibility should be to take the IDs and pass them down to NMRium, nothing more.