Inform Identity not called upon receipt of NAK response

[DanLiemanGalvion]

void (*USBPD_VDM_InformIdentity)(uint8_t PortNum, USBPD_SOPType_TypeDef SOPType,
USBPD_VDM_CommandType_Typedef CommandStatus,
USBPD_DiscoveryIdentity_TypeDef *pIdentity);

in USBPD_VDM_Callbacks is not called on receipt of a NAK response even though USBPD_VDM_CommandType_Typedef has a SVDM_RESPONDER_NAK define. This may affect other VDM Inform callbacks, but I have not had the chance to verify.

A workaround similar to that documented in #4 is likely possible since the NAK response is also at the end of the AMS(Atomic Message Sequence)

[DanLiemanGalvion]

Workaround for this issue posted #4 (comment)

[ALABSTM]

ST Internal Reference: 203379

[DanLiemanGalvion]

I will note that section 8.3.3.22.1 (Initiator Structured VDM Discover Identity State Diagram) in USBPD standard Revision 3.2, V1.1, and
8.3.3.22.1 (Initiator Structured VDM Discover Identity State Diagram) in Revision 3.1, V.15 (I don't have access to Revision 3.1, V1.7 which this library conforms to) does specify that the policy engine shall inform the Device Policy Manager of the result in the case of Discover Identity NAK/BUSY or VDMResponseTimer Timeout.