* siri/stdlib/dialyzer-supervisor/OTP-9741:
  Add test for upgrade of supervisor
  Fix dialyzer warnings in supervisor

* bjorn/deprecate-tuple-funs/OTP-9649:
  erts: Warn the first time a tuple fun is called
  otp_mibs: Eliminate use of tuple fun
  os_mon: Eliminate use of tuple fun
  asn1: Eliminate use of tuple fun
  parsetools: Eliminate use of tuple fun
  mnesia tests: Eliminate use of tuple fun
  snmp: Eliminate use of tuple fun
  wrap_log_reader_SUITE: Eliminate use of tuple fun
  big_SUITE: Eliminate use of tuple fun
  file_SUITE: Eliminate use of tuple fun
  fprof: Eliminate use of tuple fun
  xref_compiler: Eliminate use of tuple fun
  shell: Eliminate use of tuple funs
  erl_eval: Eliminate use of tuple funs
  user_sup: Eliminate use of tuple fun

* siri/stdlib/dialyzer-log_mf_h/OTP-9754:
  Fix dialyzer warning about gen_event callback init/1 in log_mf_h

The warning is about log_mf_h having a different spec for gen_event
callback init/1 than defined in gen_event.erl. log_mf_h allows return
value {error,Reason}, while gen_even only specifies successful return
values.

This commit add {error,Reason} as a valid return value to the
gen_event callback, since this is handled by the code.

Dialyzer complained over a mismatch between the callback spec of
Mod:code_change in gen_server and the spec of supervisor:code_change
(which is the implementation of a gen_server Mod:code_change).

This commit changes the callback spec to allow {error,Reason} as
return value. Also, release_handler is updated to handle this return
value.