fix -Wno_behaviours doc error in dialyzer man page

The description of the -Wno_behaviours in the dialyzer man page incorrectly
includes a "***" footnote marker, indicating that it's an option that turns
on a warning rather than turning it off. Since the option actually turns
off a warning, remove the marker. This fix makes the documentation match
that obtained from dialyzer --help.
ssh: Fix dialyzer type specs and documentation

Similar to d9ebfb8. The wrong specs were leading to dialyzer warnings
like this in our application since R16B03:

The pattern 'ok' can never match the type {'error',_}.
The pattern {'error', {'already_started', 'ssh'}} can never match the type 'ok'.
The pattern {'error', _} can never match the type {'open_error',_,string(),string()}.
Fix +Mea config
Fix alternative registry type annotations in supervisor

The type annotations for alternative registries using
the {via,Module,Name} syntax was not given for
sup_name() and sup_ref() in the supervisor module.
The type annotation was inconsistent with the
documentation and causes Dialyzer to complain about
valid supervisor:start_link and supervisor:start_child
calls.
Allow persistent option on set_env/4 and unset_env/3

An environment key set with the persistent option will not
be overridden by the ones configured in the application resource
file on load. This means persistent values will stick after the
application is loaded and also on application reload.
Merge branch 'rickard/default_acul_mod/OTP-11604'

* rickard/default_acul_mod/OTP-11604:
  Fix +Mea config
Merge branch 'josevalim/jv-persistent-set-env'

* josevalim/jv-persistent-set-env:
  Allow persistent option on set_env/4 and unset_env/3

OTP-11708
Merge branch 'calebh/fix-regestry-type-annotation'

* calebh/fix-regestry-type-annotation:
  Fix alternative registry type annotations in supervisor

OTP-11707
Merge branch 'vinoski/dialyzer-doc-fix'

* vinoski/dialyzer-doc-fix:
  fix -Wno_behaviours doc error in dialyzer man page

OTP-11706
Suppress error report when child was terminated normally

Description:
Let's assume we have a supervisor_bridge as a
non-permanent child of a supervisor. When the
bridge terminates normally it reports by
error_logger:error_report, but the supervisor does
nothing. So we have tons
(especially, when it's simple_one_for_one) of
error messages while everything is completely ok.

Let's assume we have a supervisor_bridge as a
permanent child of a supervisor. When the bridge
terminates, it invokes error_logger, but what for?
The supervisor will invoke error_logger about this
error right after that.
So what is the reason for the error_logger to log
for normally terminating children in this case?
Merge branch 'galaxie/supress-normal-terminates'

* galaxie/supress-normal-terminates:
  Suppress error report when child was terminated normally

OTP-11685
Merge branch 'weisslj/ssh-spec-doc-fixes'

* weisslj/ssh-spec-doc-fixes:
  ssh: Fix dialyzer type specs and documentation

OTP-11705