As a developer integrating IDER into my existing console, I want to have an angular component that I can add to my angular 16 based UI so that I can use the IDER features similar to how I use the KVM and SOL features of Open AMT Cloud Toolkit

Acceptance Critera

• Create IDER component similar to KVM #947
• Standalone component
• Constructor takes a config option #911 open-amt-cloud-toolkit/ui-toolkit#787 open-amt-cloud-toolkit/ui-toolkit-react#911
• Track the progress
• Explore if CD-ROM can be mounted without floppy (if not, may need a blank floppy in web UI)
• Update to Angular 17 #916
• Unit Tests
• Update Documentation

Describe the bug 🪲
A clear and concise description of what the bug is.

To Reproduce 🪜
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots 🖼️
If applicable, add screenshots to help explain your problem.

Browser Information (please complete the following information): 🖥️

• OS: [e.g. Windows 10 build 21H1, Ubuntu 20.04 LTS]
• Browser and Version: [e.g. IE Edge 95.0.1020.40 ]

Additional context
Add any other context about the problem here.

Describe the bug 🪲
When launch this sample web app and create a KVM websocket session, there needs to be a mode queryparams(https://github.com/open-amt-cloud-toolkit/mps/blob/main/src/utils/wsRedirect.ts#L36) which needs to be passed to the MPS. If not done, the device's isKVM, SOL, IDER properties will not be updated and stay false inspite of an active KVM connection.

Because of current behavior, this code does not get triggered for us. Hence the output of /api/v1/devices/redirectStatus/{guid} shows as false, false, false in spite of active KVM connection.
https://github.com/open-amt-cloud-toolkit/mps/blob/main/src/server/webserver.ts#L239

To Reproduce 🪜
Steps to reproduce the behavior:

1. Use sample UI and trigger a successful KVM connection
2. Check the output of /api/v1/devices/redirectStatus/{guid} and it should show as false, false, false.

Expected behavior
The output should be /api/v1/devices/redirectStatus/{guid} and it should show as true, false, false.

Screenshots 🖼️
If applicable, add screenshots to help explain your problem.

Webrowser KVM session:

Browser Information (please complete the following information): 🖥️

• OS: Windows 11 Pro
• Browser and Version: Chrome

Additional context
Add any other context about the problem here.

Describe the bug 🪲
The space and upper case letter characters are ignored in SOL using the Chrome browser in Windows and macOS at least.

To Reproduce 🪜
These steps show the problem; it was originally observed after Reset to BIOS entering a password that contained upper case characters. The 'space' problem was observed attempting the use the space bar as the "any Key" to a BIOS prompt.

Steps to reproduce the behavior:

1. Make an SOL connection to a device.
2. On the device, open putty or terminal of choice and connect to the SOL COM port.
3. In the SOL window, type "Hello Polly!"
4. On the device, "elloolly!" appears in the putty/terminal window.

The reverse isn't true, all characters tested so far will be transmitted from the device.

Expected behavior
All characters to be sent to the device.

Browser Information (please complete the following information): 🖥️

• OS: Windows 11, macOS
• Browser and Version: Chrome 105.0.5195.125

Additional context

The problem occurs whether Caps-Lock or Shift is used for A-Z.

Note that pasting A-Z and ' ' into the SOL window does work indicating it's likely a keyboard handling problem... investigation reveals that this is all probably due to the custom key handler in terminal.component.ts:

    this.term.attachCustomKeyEventHandler((e: any) => {
      e.stopPropagation()
      e.preventDefault()
      if (e.ctrlKey === true && e.shiftKey === true && e.keyCode === C) {
        return navigator.clipboard.writeText(this.term.getSelection())
      } else if (e.ctrlKey === true && e.shiftKey === true && e.keyCode === V) {
        return navigator.clipboard.readText().then(text => {
          this.handleKeyPress.emit(text)
        })
      } else if (e.code === SPACE) {
        return this.handleKeyPress.emit(e.key)
      }
    })

and the following code in xterm's _keyDown():

    // HACK: Process A-Z in the keypress event to fix an issue with macOS IMEs where lower case
    // letters cannot be input while caps lock is on.
    if (event.key && !event.ctrlKey && !event.altKey && !event.metaKey && event.key.length === 1) {
      if (event.key.charCodeAt(0) >= 65 && event.key.charCodeAt(0) <= 90) {
        return true;
      }
    }

First, e.code is being compared against SPACE. Either it should be compared against "Space" or e.keyCode compared against SPACE as in the comparisons against C and V. Since keyCode is deprecated, it should probably be the former.

Secondly, the custom key event handle is calling preventDefault(). xterm is relying on getting keypress events for A-Z and preventDefault() appears to be preventing them. At least Chrome developer tools don't show xterm's _keyPress() being called... This can probably be fixed by only calling preventDefault() for Ctrl-Shift-[CV] and 'space'. Hopefully that wouldn't become a problem if xterm changed their 'HACK'.