feat(108): Stream Request and Response Bodies

[SoulKa]

Changes

• Use latest LTS of node, which is Node22
• Create IpcPushStream class in renderer, which receives stream data pushed to the renderer (a pull stream would be a stream that supports read())
• Create event handler in main process that opens streams and sends their data chunk by chunk to renderer
• Remove unused event handler methods for reading files
• Fix binding of ipcRenderer methods in context bridge
• Implement abstract EventEmitter class in renderer
• Fix switching requests and losing changes of request body

Testing

• Switch between requests and see the request body being loaded
• Send request and see response being loaded

Checklist

• Issue has been linked to this PR
• Code has been reviewed by person creating the PR
• Commit messages, branch names, code formatting adheres to our Contributing Guidelines
  
• Automated tests have been written, if possible
• Manual testing has been performed
• Documentation has been updated, if necessary
• Changes have been reviewed by second person

[kwerber]

What is the reason that we have not used main-event-service for the stream events? Do we need to have "lower level access" for performance or code readability reasons? Is the main-event-service abstraction unfit for this purpose?

[SoulKa]

What is the reason that we have not used main-event-service for the stream events? Do we need to have "lower level access" for performance or code readability reasons? Is the main-event-service abstraction unfit for this purpose?

The main-event-service only supports ipcMain.handle() for an equivalent invoke() on the renderer side. But I also need ipcMain.on(). Also, the main event handler has only "public" methods. I do not want to expose the stream.close() method globally. This should only be called by the stream internally.