issues in GetARDiagnosis service

Issue 1

The GetARDiagnosis service indicates a non-zero timestamp for WriteRecord indication sent to application in unexpected situations.

Either if there was no WriteRecord Indication generated to host at all (in which case the timestamp needs to be 0), or if there were additional WriteRecords handled by protocolstack after the last of application.

If no WriteRecord Indication is pending at application, the timestamp shall be 0.

Issue 2

The service returns 2 states: ArState and CmdevState

Currently, ArState returns the "CMDEV state from specification" while CmdevState returns the "CMDEV_State_ind from specification". To not get confused, this should be switched. The variable CmdevState shall return the actual "CMDEV state from specification".

Issue 3

When a WriteRequest is pending to application, the timestamp for CMDEV-event is set in parallel to the one for WriteRecord-event. This is unexpected, they should not be set in parallel.