Fix httpd config option 'script_timeout'

This fixes the usage of the httpd configuration option 'script_timeout',
which got ignored before.

The documentation states that the value is in seconds, which was true
when using the Apache like configuration file, but not true when using
the proplist style configuration.
Remove ^L characters hidden randomly in the code. Not those used in text files as delimiters.

While working on a tool that processes Erlang code and testing it against this repo,
I found out about those little sneaky 0xff. I thought it may be of help to other
people build such tools to remove non-conforming-to-standard characters.
Add some more comments about what the test does

This changed the lines so the results now differ.
Fix a comment
Adopt a convention about unknown modules
Use the modern version of is_subtype
No reason for calls to unknown modules
Adopt a convention about unknown modules
Fix crash when using remote types in the tail of list types

Hans Bolider reported a dialyzer crash when using a remote type in
the tail position of a maybe_improper_list() declaration. A test
was created (by extending an existing module of the testsuite)
and erl_types was modified to expand the remote type and not pass
it unexpanded to subsequent phases in the processing.
Merge branch 'maint'
Merge branch 'kostis/dialyzer_R16B02_fixes/OTP-11374' into maint

* kostis/dialyzer_R16B02_fixes/OTP-11374:
  Fix crash when using remote types in the tail of list types
  Adopt a convention about unknown modules
  No reason for calls to unknown modules
  Use the modern version of is_subtype
  Adopt a convention about unknown modules
  Fix a comment
  Add some more comments about what the test does
Merge branch 'maint'
Merge branch 'fenollp/treewide_remove_unexpected_0xff/OTP-11323' into maint

* fenollp/treewide_remove_unexpected_0xff/OTP-11323:
  Remove ^L characters hidden randomly in the code. Not those used in text files as delimiters.
Merge branch 'maint'
Support non top level letrecs in dialyzer

Dialyzer so far only supported letrecs at the top-level
and comprehension-like letrecs (i.e. that were directly applied)
in their body.

This commit address this issue by storing in the callgraph
bound letrec labels pointing to their functions. This information
is then used by the dataflow to properly lookup recursive
definitions.
EEP 37: Funs with names

This adds optional names to fun expressions. A named fun expression
is parsed as a tuple `{named_fun,Loc,Name,Clauses}` in erl_parse.

If a fun expression has a name, it must be present and be the same in
every of its clauses. The function name shadows the environment of the
expression shadowing the environment and it is shadowed by the
environment of the clauses' arguments. An unused function name triggers
a warning unless it is prefixed by _, just as every variable.
Variable _ is allowed as a function name.

It is not an error to put a named function in a record field default
value.

When transforming to Core Erlang, the named fun Fun is changed into
the following expression:

    letrec 'Fun'/Arity =
               fun (Args) ->
                       let <Fun> = 'Fun'/Arity
                       in Case
    in 'Fun'/Arity

where Args is the list of arguments of 'Fun'/Arity and Case the
Core Erlang expression corresponding to the clauses of Fun.

This transformation allows us to entirely skip any k_var to k_local
transformation in the fun's clauses bodies.
Test named funs