common_test: Fix exported types

* inet:host_name() -> inet:hostname()
* ct:hook_options() -> ct_netconfc:hook_options()
[test_server,common_test] Fix cross cover mechansim

Update the interface for cross cover analysis (collection of cover
data over multiple tests) so it can be used via common_test and
directly with test server.

The concept of 'application' in the cross cover interface is removed
and replaced with an arbitrary Tag=atom() which identifies a test run.
[common_test] Add test case for cross cover mechanism
[common_test] Add documentation for cross cover analysis
Merge branch 'egil/fix-dialyzer-specs/OTP-10601'

* egil/fix-dialyzer-specs/OTP-10601:
  common_test: Fix exported types
[common_test] Fix cth_surefire

The following corrections/changes are done in the cth_surefire hook:

* Earlier there would always be a 'properties' element under the
  'testsuites' element. This would exist even if there were now
  'property' element inside it. This has been changed so if there are
  no 'property' elements to display, then there will not be a
  'properties' element either.

* The XML file will now (unless other is specified) be stored in the
  top log directory. Earlier, the default directory would be the
  current working directory for the erlang node, which would mostly,
  but not always, be the top log directory.

* The 'hostname' attribute in the 'testsuite' element would earlier
  never have the correct value. This has been corrected.

* The 'errors' attribute in the 'testsuite' element would earlier
  display the number of failed testcases. This has been changed and
  will now always have the value 0, while the 'failures' attribute
  will show the number of failed testcases.

* A new attribute 'skipped' is added to the 'testsuite' element. This
  will display the number of skipped testcases. These would earlier be
  included in the number of failed test cases.

* The total number of tests displayed by the 'tests' attribute in the
  'testsuite' element would earlier include init/end_per_suite and
  init/end_per_group. This is no longer the case. The 'tests'
  attribute will now only count "real" test cases.

* Earlier, auto skipped test cases would have no value in the 'log'
  attribute. This is now corrected.

* A new attributes 'log' is added to the 'testsuite' element.

* A new option named 'url_base' is added for this hook. If this
  option is used, a new attribute named 'url' will be added to the
  'testcase' and 'testsuite' elements.

Tests are added for the ct_surefire hook.
[common_test] Add documentation of new url_base option to cth_surefire
Prepare release
[common_test] Extend valid interval for approximate timer values in tests

When matching the result of tests of timetrap timeouts, the actual
time is measured against the expected time, and an interval of +/- 2%
was seen as correct result. This turned out to fail on some platforms
and is now changed to 5%.
[common_test] Extend timeout values for slave nodes in ct_master_SUITE

Some tests in ct_master_SUITE failed on some platforms with
boot_timeout when trying to start slave nodes. The default timeout
value was 3 seconds, and it is now extended to 10 seconds in these
tests.

To avoid similar errors with init_timeout and startup_timeout, these
are both exteded from 1 second default value to 10 seconds in this
test.
[common_test] Changed call to publick_key to use documented interface

Earlier used 'OTP-PUB-KEY':encode/2 - now public_key:der_encode/2 instead.
[common_test] Avoid hanging ct@host node if crypto does not exist

ct_netconfc:init_per_suite called ct_test_support:init_per_suite
before checking if crypto exists. This caused the slave node (ct@host)
to be started even though the suite would be skipped when crypto did
not exist - which in turn caused a hanging ct node since end_per_suite
is not run in a skipped suite. This has been corrected.
[common_test] Extend timetrap time in ct_hooks_SUITE

This suite often fails with timetrap timeout on some test machines.
Merge branch 'maint-r15' into maint
Merge branch 'maint'

Conflicts:
	lib/common_test/test/Makefile
[common_test] Adjust window after netconf client receives data

If ssh_connection:adjust_window/3 is not called after each time data
is received in the netconf client, the client will eventually stop
receiving data. This bug has been corrected.
[common_test] Stop cover on slave node after node is terminated

Before terminating slave nodes, common_test calls cover:flush/1 to
fetch data from the node without actually stopping cover on this
node. If cover is not stopped for the node and a new node with the
same name is started, then cover will be started on the new node. To
avoid this common_test now calls cover:stop/1 after the slave node is
terminated.
Add test case to verify that config data gets properly restored
Add verification terms in test suite

OTP-10070
Prepare release