Make erlang-mode more compatible with package.el

Package.el  and Emacs  package  repositories (like  ELPA or  Marmalade
place some requirements onto packages which are uploaded to them. This
commit does  minor cosmetic  changes which makes  it easier  to create
appropriate package file for those repositories.
Remove Erlang-specific compilation error regexp

The purpose of this regexp is to ensure that, when invoking the Erlang
compiler inside Emacs through M-x compile, any error messages be
turned into links jumping to the right line in the right source file.
However, it seems like this works out of the box in modern Emacsen,
and furthermore, using a non-standard regexp inhibits jumping to a
certain column when this is provided by the compiler.
Merge branch 'mh/remove-compilation-error-regexp'

* mh/remove-compilation-error-regexp:
  Remove Erlang-specific compilation error regexp

OTP-10168
Merge branch 'maint'
Merge branch 'maint'

* maint:
  Allow non-ASCII characters in Xref filanmes
Merge branch 'maint'
Merge branch 'maint'
Merge branch 'maint'

Conflicts:
	lib/diameter/autoconf/vxworks/sed.general
	xcomp/README.md
Merge tag 'OTP_R15B02'

The R15B02 release
Merge branch 'maint'
Merge branch 'gp/make_erlang_mode_elpa_friendly'

* gp/make_erlang_mode_elpa_friendly:
  Make erlang-mode more compatible with package.el

OTP-10465
Add separate face for exported functions

Add a separate face for exported functions to erlang mode so that they
are distiguishable at a glance. By default, the face is identical to
that of normal functions and there is also a configuration variable to
inhibit the face in case running this on a low-performance machine is
too slow.
[cover] Add support for test_server

OTP-10523

* Added cover:flush(Nodes), which will fetch data from remote nodes
  without stopping cover on those nodes.

* Added cover:get_main_node(), which returns the node name of the main
  node. This is used by test_server to avoid {error,not_main_node}
  when a slave starts another slave (e.g. in test_server's own tests).
[cover] Don't kill remote nodes when connection to main node is lost

OTP-10523

Since the will probably be cover compiled modules left in the remote
node, we want to keep the cover_server and it's ets tables even if
connection to remote node is lost. This way it will not crash (due to
ets:insert in non existing table) if functions in cover compiled
modules are executed.
[cover] Allow reconnection if node has been disconnected or down

OTP-10523

Earlier, if the connection to a remote cover node was lost, all cover
data was lost and the cover_server on the remote node would die. This
would cause problems if there were cover compiled modules that would
still be executed since they would attempt to write to the no longer
existing ets tables belonging to the cover_server.

This commit changes this behavior so that the cover_server on the
remote node will survive connection loss and continue collecting cover
data. If the connection is re-established then the main node will sync
with the remote node again and cover data will not be lost (unless the
node was down).
Merge branch 'maint'
Fix various doc typos for R16
Merge branch 'tja/exported-function-face'

* tja/exported-function-face:
  Add separate face for exported functions

OTP-10637
[cover] Don't mark stopped node as lost

Nodes that were stopped with cover:stop/1 were marked as lost and
would be reconnected if a nodeup was later received for a node with
the same name. This has been corrected.
[cover] Remove stopped node also from lost_nodes list

A nodes that was stopped with cover:stop/1 while marked as lost would
not be removed from the list of lost nodes. Therefore, if a nodeup was
later received for a node with the same name, it would be
reconnected. This has been corrected.