* ks/hipe-cleanup-escaping/OTP-11031:
  Loosen the assumptions of code that handles escaping functions

The HiPE compiler implicitly relied on the assumption that a function
will never appear as both exported and also used as function closure.
This was true because the BEAM compiler prior to R16B created module
local anonymous functions for each closure. A proposed change to the
BEAM compiler invalidates this invariant, so in order to accommodate
for this change there needs to be a change of how the set of possibly
escaping functions is computed.

While doing this, the code was simplified by taking out a boolean()
tag that indicated whether a function is a closure or exported and
also slightly cleaned up the affected modules.

The following module produced erroneous results when compiled with HiPE:

-module(a).
-export([foo/1]).

foo(X) when is_number(X) ->
    is_integer(X).

Running:

  1> c(a).
  2> a:foo(0).
  true
  3> hipe:c(a).
  4> a:foo(0).
  false      % *** WRONG ***

The problem was that the 'number' case for the `hipe_icode:type_test/1`
was going to the default case where the argument was determined as being
something other than an integer. Thanks to Sebastian Egner and Johannes
Weißl for bringing the bug into attention. Fixed on the day it was reported.

Conflicts:
	lib/diameter/autoconf/vxworks/sed.general
	xcomp/README.md