Changes

erab_fsm: log the creation event and UID

When looking at GSMTAP logging, it's oftentimes useful to see
the beginning of a lifecycle of an E-RAB FSM.

Change-Id: I5746a645d95c9c931c24ebc170ef88cd38311542
Related: SYS#7738

sctp_proxy: move catch-all for SCTP events to handle_event/4

Reduce code duplication and prepare for handing of sctp_error.

Change-Id: I8f42a31fdf4a4e01106ace81d87188a340fe7c83
Related: SYS#7738

sctp_{server,proxy}: handle sctp_error messages from gen_sctp

The `{sctp_error, ...}` message is undocumented, but it does exist,
and we have encountered it in production.  The logic that generates
`{sctp, ...}` and `{sctp_error, ...}` messages resides in Erlang/OTP's
inet_drv.c, specifically in packet_binary_message() and
sctp_parse_async_event().  Within sctp_parse_async_event(), an error
is indicated by replacing the initial `sctp` atom with `sctp_error`.

Currently the following SCTP events are treated as errors:

* SCTP_SEND_FAILED (becomes #sctp_send_failed{}),
* SCTP_REMOTE_ERROR (becomes #sctp_remote_error{}),
* SCTP_PARTIAL_DELIVERY_EVENT (becomes #sctp_pdapi_event{}).

Print more specific messages when the sctp_error is received.
Add new metrics for the above-mentioned SCTP events.

Change-Id: I38203d915d54dacd4e9bbf158ab86f8936585a34
Related: SYS#7738