Adding a timeout for Named Pipe connection to the Pahkat Service #50

[alvskar]

To help with #50

This is intended to add a 2s timeout for the connection to the Pahkat Service Named Pipe and an associated message box informing the user that the Windows Service is down if the connection fails, and then closing the program (same as what appears to be intended startup behavior but that code was never hit).

This may not address #50 completely depending on what the cause is, but I have not been able to replicate the issue otherwise. Currently, if the Windows Service is down, Divvun Manager just waits forever, on the All Repositories page or any other relevant page since there's never any cancellation information sent. This change should help narrow down if the issue is related to that.

[alvskar]

This might also be relevant to #15 and #17 , seem to be a string of issues around UI and Windows Service race conditions.

[divvun-taskcluster]

Uh oh! Looks like an error! Details

Task RvUKImUASRKBUs5hdb66ug can't be rescheduled past its deadline of 2023-05-17T12:46:14.099Z.

---

• method: rerunTask
• errorCode: RequestConflict
• statusCode: 409
• time: 2023-05-17T13:18:20.373Z