Client frontend: issue when a PublishResponse is received after DeleteSubscriptionResponse
Description
In case a PublishResponse is received after the DeleteSubscriptionResponse, the client front end might crash on the following assertion in StaMac_ProcessMsg_PublishResponse
:
assert(!pSM->bAckSubscr);
Analysis
If a PublishResponse is evaluated after a DeleteSubscription, we might evaluate the response with an incoherent context around the subscription. To avoid it, we should reset all context associated to subscription and ignore any PublishResponse after this point until a new subscription is created.