[test_server] Add Config to run_test_case_msgloop/1 from the start

Earlier, #st.config was set to undefined when entering this loop. Then
it was updated when the test case itself started. This means that if
the test case process crashed during test case initiation, the parent
process would not know the Config.

This commit saves the initial Config value in the parent process
(run_test_case_msgloop/1) from the start.
[test_server] Skip test cases if init_per_group fails in user timetrap

'user_timetrap_error' was not detected during any "conf init function"
except init_per_suite, so if e.g. init_per_group failed with
user_timetrap_error, then the test cases in the group would not be
skipped. This has been corrected.
[common_test] Add tests for user timetraps in groups
Merge branch 'siri/user_timetrap-group-test/OTP-10018'

* siri/user_timetrap-group-test/OTP-10018:
  [common_test] Add tests for user timetraps in groups
  [test_server] Skip test cases if init_per_group fails in user timetrap
  [test_server] Add Config to run_test_case_msgloop/1 from the start
New setup in testing idle_time
Make sure that "Testing..." is not written if testing has finished

When writing messages to stdout, all messages are prefixed with
"Testing" followed by the name of the test suite. We don't want
to write that prefix if testing has stopped.
Make sure that "Cover analysing..." is written to stdout

If it is written with io:fwrite/2 it will be written to
the unexpected_io log, where it will not be of any use.
Handle ct:abort_current_testcase/1 when executing parallel groups

ct:abort_current_testcase/1 (which is a wrapper for the function
with the same name in test_server_ctrl) would not work as expected
when a group with parallel test cases was executing. Essentially,
the abort_current_testcase message would be ignored until the group
has finished and would then abort the end_per_group testcase for
the group.

Since there is no unique current testcase when a parallel group is
executing, we must handle the abort_current_testcase message and
return an error tuple.

Also fix the bug that test_server_ctrl:abort_current_testcase/1
would always return 'ok'.
test_server_io: Correct a few comments
sets_SUITE: Eliminate use of parameterized modules

Since the support for parameterized modules will be removed in R16,
we should not use them in test cases.
dict_SUITE: Eliminate use of parameterized modules

Since the support for parameterized modules will be removed in R16,
we should not use them in test cases.
Merge branch 'bjorn/stdlib/eliminate-param-module-use'

* bjorn/stdlib/eliminate-param-module-use:
  dict_SUITE: Eliminate use of parameterized modules
  sets_SUITE: Eliminate use of parameterized modules
Merge branch 'maint'
Merge branch 'maint'
Remove stale support for remote target nodes

The support for remote target nodes has not worked in a long time.
We are unlikely to ever need remot target node support and if
we'll need it will be easier to start over from scratch.
Merge branch 'bjorn/test_server/remove-remote-target-support'

* bjorn/test_server/remove-remote-target-support:
  Remove stale support for remote target nodes
Merge branch 'bjorn/ct/minor-corrections'

* bjorn/ct/minor-corrections:
  test_server_io: Correct a few comments
  Handle ct:abort_current_testcase/1 when executing parallel groups
  Make sure that "Cover analysing..." is written to stdout
  Make sure that "Testing..." is not written if testing has finished
Merge branch 'maint'

* maint:
  Fix binary append exceptions
Merge branch 'maint'

* maint:
  Doc for quiet_mode
  SSH quiet mode
Support ANSI in the console