The EdgeWebDriver does not properly handle signals such as SIGTERM and SIGINT, resulting in sessions not being cleaned up correctly.

[bukowa]

Expected Behavior:

When a SIGTERM or SIGINT signal is received (for example, when terminating the WebDriver process gracefully), EdgeWebDriver should properly clean up all active sessions and resources associated with them.

Actual Behavior:

Currently, sending a SIGTERM or SIGINT signal to EdgeWebDriver does not ensure that all sessions are cleaned up correctly. This can lead to resource leaks and inconsistent behavior when running multiple test sessions sequentially. The underlying binaries and their webviews are not killed.

Steps to Reproduce:

Start EdgeWebDriver and initiate one or more WebDriver sessions.
Send a SIGTERM or SIGINT signal to EdgeWebDriver (e.g., using kill command on Unix-like systems or closing the process on Windows).
Observe whether all WebDriver sessions and associated resources are properly cleaned up or if some sessions remain active.

Additional Information:

EdgeWebDriver version: 126.0.2592.81 (38151611195b9357be892bf1ae5c4b7942a1b216)

Proposed Solution:

Ensure that EdgeWebDriver gracefully handles SIGTERM and SIGINT signals to properly clean up all WebDriver sessions and associated resources before exiting.