3.1r1: 9.5.1's TCP network tests

[jadamcrain]

Implements 3.1r1's 9.5.1 TCP tests: Port 20000, Port Other Than 20000, Specific IP Address and Wildcard IP Address. This is the first part of section 9; the UDP tests (9.5.1.5, 9.5.1.6, 9.5.2 to 9.5.4) follow.

Every network test is gated by configuration: it runs only where its network.* options say the device and the test bench can do what it tests, and is skipped otherwise. That includes Port 20000, which 3.1r1 requires of every TCP device.

Harness

• The driver can connect from a given local address and port (TestDriver.connect). It can also probe a connection the device shouldn't accept (TestDriver.probe):
  • the probe passes if the device refuses the connection, doesn't accept it within the response timeout, or accepts it and closes it without answering REQUEST LINK STATUS;
  • it fails if the device keeps the connection open.
• A procedure can now have cleanup steps. The runner runs them however the procedure ends, including after a failure or an interruption. The network tests use them to restore the device's network. If a cleanup step fails, a procedure that otherwise passed fails.
• If the test bench can't use a local address (LocalBindException), the run aborts as a harness failure. The device isn't failed for it.
• Packet capture now filters on the device's address instead of its port, so it captures the network tests' other ports too.

Plugin. Three new IntegrationPlugin methods. Their defaults throw, and DefaultIntegrationPlugin prompts for them:

• configureNetwork(NetworkSetup) takes the whole setup: transport, port and allowed masters, plus the UDP destinations the later tests use, so the API won't change for them;
• restoreNetwork puts back the device's usual network setup;
• verifyDisconnectNoticed checks that the device noticed the master closing its connection.

Options. A new network group:

• network.master.address is the address of this host the tests connect from;
• capability flags: network.tcp, .tcp.configurablePort, .tcp.specificAddress, .tcp.wildcard and .tcp.anyAddress;
• the wildcard test's range and addresses.

The configuration check requires these, for the network tests that will run, and requires the wildcard test's addresses to be distinct.

The 2.7 -describe output is unchanged.