LWm2m: Avoid unnecessary unavailability alarms for LwM2M device

Description:
For LWm2m devices, the expected transmission interval (Required interval) is currently linked to the registration lifetime and it doesn't matter what is entered in the GUI, this value is always be overwritten by the "LwM2M Server Lifetime" object.
This means that the actual that parameters "Registration Lifetime" and "Required interval" (expected transmission interval) cannot be set for lwm2m independently of each other. This leads to thousands of unnecessary unavailability alarms in LwM2M in the field.
For example:
If you wants to monitor devices and record possible outages via a fault management and
unavailability alarm comes constantly, because the devices in the Nb-IoT do not send so reliably, this monitoring makes no sense.
In this case the acceptance for this alarm type is zero, since here simply the real circumstances are not taken care of.

As explained, the two parameters should be configurable independently of each other. Especially with regard to flexibility and, above all, practicality in operation.

Actual:

• Parameters "Registration Lifetime" and "Required interval" (expected transmission interval) in CoT cannot be set for lwm2m independently of each other.

• Thousands of unnecessary unavailability alarms in LwM2M are triggered.

After implementation of the AHA request:
Parameters "Registration Lifetime" and "Required interval" (expected transmission interval) can be set independently of each other for lwm2m.

Thanks