* anders/diameter/18.2/OTP-13180:
  vsn -> 1.11.1
  Update appup for 18.2

* anders/diameter/request_leak/OTP-13137:
  Fix request table leak at retransmission
  Fix request table leak at exit signal

In the case of retranmission, a prepare_retransmit callback could modify
End-to-End and/or Hop-by-Hop identifiers so that the resulting
diameter_request entry was not removed, since the removal was of entries
with the identifiers of the original request. The chances someone doing
this in practice are probably minimal.

The storing of request records in the ets table diameter_request was
wrapped in a try/after so that the latter would unconditionally remove
written entries. The problem is that it didn't deal with the process
exiting as a result of an exit signal, since this doesn't raise in an
exception. Since the process in question applies callbacks to user code,
we can potentially be linked to other process and exit as a result.
Trapping exits changes the current behaviour of the process, so spawn a
monitoring process that cleans up upon reception of 'DOWN'.

OTP-13137 request table leak

No load order requirements (one file).

* anders/diameter/18.1/OTP-12978:
  Update appup for 18.1

* anders/diameter/watchdog/OTP-12969:
  Fix watchdog function_clause

* anders/diameter/M-bit/OTP-12947:
  Add service_opt() strict_mbit

OTP-12947 strict_mbit service_opt()
OTP-12969 diameter_watchdog function_clause

No load order requirements.

Commit 4f365c07 introduced the error on set_watchdog/2, as a consequence
of timeout/1 returning stop, which only happens with accepting
transports with {restrict_connections, false}.