Don't lose the extension mark for object set parameters

When an object set is an actual parameter, the extension marker
for the object set could get lost.
Prevent loss of objects after the extension marker

In an object set with a single root object, objects after
the extension marker would be lost.
Fix rest_for_one and one_for_all restarting a child not terminated

In rest_for_one and one_for_all supervisors one child dying can cause
multiple children to be restarted. Previously if the child that caused
the restart is started successfully but another child fails to start,
the supervisor would not terminate this child with the other
successfully restarted children as no record of the pid was kept. Thus
the supervisor would try to start this child again. This could lead to
multiples of the same child or if the child is registered cause repeated
attempts at starting this child - until the max restart threshold was
reached.

Now the child that failed to start becomes the restarting child, instead
of staying with the same child, for the next restart attempt. This has
the following side effects:

1) In one_for_all the new version of the child that original died is
   terminated before a restart attempt is made.

2) In rest_for_one all succesfully restarted children are not terminated
   and restarting continues from the child that failed to start.
Use erlang:demonitor(Ref, [flush]) where applicable
inets: stop block timer with the right arguments
Merge branch 'lh/demonitor-flush/OTP-11039' into maint

* lh/demonitor-flush/OTP-11039:
  Use erlang:demonitor(Ref, [flush]) where applicable
Merge branch 'jaf/fix-supervisor-multi-restart/OTP-11042' into maint
Merge branch 'bjorn/asn1/fix-lost-extension-mark/OTP-10995' into maint-r15

* bjorn/asn1/fix-lost-extension-mark/OTP-10995:
  Prevent loss of objects after the extension marker
  Don't lose the extension mark for object set parameters
Prepare release
[common_test] Use max importance when logging errors

This commit adds ?MAX_IMPORTANCE to error notifications in the test
case log, and it makes sure that the printout says "CT Error
Notification".

Printouts from cth_log_redirect (sasl and error_reports) uses
?STD_IMPORTANCE and states "System" in the printout.
[common_test] Add link from red error notification to full error description

In test case log, the red error notification may sometimes be
truncated. This commit adds a link from this printout to the end of
the log where the full error description and stacktrace i written.
Do not count offline run-queues as empty
Merge branch 'bjorn/asn1/fix-lost-extension-mark/OTP-10995' into maint-r16

* bjorn/asn1/fix-lost-extension-mark/OTP-10995:
  Prevent loss of objects after the extension marker
  Don't lose the extension mark for object set parameters
Encode Erlang source files with non-ascii characters in UTF-8

To ensure that 'master' compiles when we merge 'maint' to it,
regardless of which encoding is default in 'master', all source
files with non-ascii characters *must* have the encoding specified.
Merge branch 'bjorn/fix-encoding/OTP-11041' into maint

* bjorn/fix-encoding/OTP-11041:
  Encode Erlang source files with non-ascii characters in UTF-8
Implement cache for the CT logger

OTP-10855
Merge branch 'peppe/common_test/log_cache' into maint

* peppe/common_test/log_cache:
  Implement cache for the CT logger

OTP-10855
Bug fixes in Common Test log cache
Merge branch 'peppe/common_test/log_cache2' into maint

* peppe/common_test/log_cache2:
  Bug fixes in Common Test log cache
Add documentation of w, i and e addition to +fnu and +fna switches to erl

These were documented in the stdlib user's guide, but not in the
reference manual for erl. This has now been corrected.