IECHost GUI client

This is something that was noted by users before, including in the readme.txt of Mwc (https://csdb.dk/release/?id=42644&show=summary), where it reads:

"WarpCopy64 is not always successful when attempting to move the R/W head to track 1. As opposed to the original WarpCopy client, mwc tries to use the Commodore DOS to move the R/W head to track 1. This seems to be more stable than the original WarpCopy64 method, but may still fail. This can typically be seen if mwc reports errors in tracks 18, 25 and 31 when attempting to transfer a disk. The situation can often be remedied by explicitly moving the R/W head to track 1, e.g., by issuing "@br 01 00" in the Action Replay monitor, before restarting the WarpCopy64 server program."

The root issue seems to be that when the WarpCopy drive code tries to detect what track the drive's head is currently on, it does not try to switch read density, hence such detection might produce the wrong result.

The mitigation that was provided in the IECHost GUI client consists in the "Pre-initialize disk" option. Its effectiveness is under scrutiny at the moment but communication with users is quite slow.

A proper navigation fix is in the works. Unfortunately I haven't got access to a disk suitable for development or testing. I might be able to create a synthetic one though. For this reason this bug is being moved to a later milestone.