Changes

mtp: Improve mtp_sap/ss7_user APIs

* The ss7_user API was so far never used externally, and internally only
  by SCCP and a unit test. It has several bad practices like first
  passing a inst parent ptr to allocate it, and then require a inst
  pointer again to operate on it (eg. register/unregister, send a
  primitive, etc.). This only makes the API more complex than needed and
  creates potential problems where a isnt differnet than the one ss7_user
  was allocated on is passed. Instead, the ss7_user is pinned to its
  parent inst during alloction, and all MTP-SAP always happens uniquely
  through the ss7_user. This follows much more closely the already
  sanitized and much more used sccp_sap/sccp_user APIs.

* Move more primitive/SAP related code to mtp_sap.c, to make it easier to
  spot where the inter-layer communication happens. This way we also have
  the same disposition as with sccp_sap/sccp_user.

* Clean up some primitive related APIs to unify naming with other usual
  SAP/primitive osmocom code.

Change-Id: If320db2bcec7ccbbc2cdac0cbf018fd8be7bde22

mtp: Introduce mtp_prim_* API helpers

This allows keeping more API related packing inside mtp_sap.c, as well
as provide public API to be able to submit a MTP-TRANSFER.req from
outside of the library (which will be used by osmo-bsc to submit
MGCP/CTRL over IPA in SCCPLite).

Change-Id: I4af154a65b8c23b9e8647845337ad1b5aa3901aa

mtp: Submit MTP-RESUME/PAUSE.ind up over MTP SAP

This allows supporting MTP users other than existing internal SCCP
stack.

Change-Id: If4360f07aa199e84c57820957ddde4259d1c92ce

mtp: Submit MTP-STATUS.ind up over MTP SAP

This allows supporting MTP users other than existing internal SCCP
stack.

Change-Id: I5e810451481e50f2942b3a1bf88212326b8d124e