BSOD seemed to occur sometimes while a partial urbr is processed. See #222.
There was a race condition between store_urbr_partial() and urbr cancellation.
This commit will unmark cancelable before processing a partial urbr in order to
avoid such a race.

My speculation of skipping IN TRANSFER CMD_SUBMIT packets was
wrong. Now all CMD_SUBMIT packet directions are being cached and
if a cache entry is overwritten (cache too small, ...), the cache
retrival returns original packet header direction value.

This is a 'usbip_header_basic' cache to hold transfer direction of
all OUT CMD_SUBMIT packets. Cache info is used when RET_SUBMIT
packets with the same sequence number arrive.
The transfer direction, EP address and device ID are not provided
in return RET_SUBMIT packets from Linux, when used as an USBIP
server.

Cache entries of this cache are never deleted. The cache entry
location is simply overwritten on every sequence number being
increased by the number of all cache entry locations.
This cache has constant cache entry R/W access time (no search).

The data buffer is not present in RET_SUBMIT packets of OUT ISOCH
transfers.

Attached port can be checked if it is still connected or not by using
port command of usbip.exe with '-p' option. An external program can
diffentiate with an exit code. #186

The prior attach command was blocked not showing a command prompt.
This behavior used to lead a user to misunderstand that attach command
does not work. So, a new attacher.exe is introduced to execute a
forward routine in a separate process. As a side benefit, attach
command is able to report an assigned port. A new attach command has
'-t' option, which displays a port number only. It would be helpful
to write an external script or program to utilize usbip.exe.

related issues: #202, #186

Resource files of userspace tools are only required for version
information. All unnecessary stuff are cleared out.

When usbip.exe was killed abruptly, a port of vhci(ude) was not
reclaimed. Thus vhci(ude) calls plugout at UDE cleanup routine
if not called. Ctrl+C in attach command does not suffer from this
problem. In that case, unplugging is called by a forwarder by
catching a signal.

Maximum # of ports of vhci(ude) was 4. It was relatively small?
Now, ports number is raised to 16.
Attach command will show a proper error message when port full occur.

The version of vhci_ude is updated to 0.3.3, which was missed by
mistake. In addition, some debugging message formats were fixed.

When usbipd executes in no debug mode, verbose debugging messages
are suppressed.

usbip command did not present user friendly message. Messages suitable
for debugging were displayed together with informative error messages.
Thus, all debugging messages goes to dbg() not err().
This commit also clarifies error messages for attach/detach/list
command.

Some usbip error codes are newly added from up-to-date linux sources.
usbipd can report ST_NODEV error code for a non-existent bus id.

A USB serial can be overwritten by -s option of usbip.exe.
Old -i option of usbip.exe is changed to -s option in order to
emphasize USB serial.

port number of linux vhci starts from 0. Thus usbip-win complies linux
assignment rule. An old vhci used port number 0 as a mark for detaching
all devices. Now, detaching with '*' as a port value will detach all
devices.

install_ude and uninstall_ude are removed from commands of usbip.exe.
Now install command can handle both vhci versions(wdm and ude).

attach_ude command of usbip.exe is removed. Instead, attach command
can be used for vhci(ude).

usbip.exe and usbipd.exe can clean up a usbip session when a peer goes
away due to network failure or system error. Abortive disconnection is
detected by utilizing TCP KEEPALIVE packet. KEEPALIVE packet is sent
by KEEPALIVE_TIMEOUT environment variable.

Version 0.3.2. Now usbip.exe, usbipd.exe have version resources.

If setting interface fails for a being detached device, vusb does not
be cleaned up. So, dynamic interface setting is avoided for an
invalidated device.

When a device is actively running with iso transfer, detach process is
used to be freezed. This is due to that iso transfers are requested
to the plugged-out device. Therefore, let an invalidated vusb deny
a subsequent request.

There was a race condition between WDF req cancellation and detach
command. urbr completion is decomposed into 2 steps: unmarking cancel
& completing WDF req.

Spinlock range of vhci(ude) was too broad when plugin & plugout are
executed. Spinlock range is narrowed down. This would help to reduce
DISPATCH IRQL range.