Instead of triggering /v1/dispose-remainders-of-deregistered-application , subscription shall be removed for unsuccessful regard-applications

[PrathibaJee]

If OKM could not able to regard an application due to any internal failure ,
then
as of now OKM will send /v1/dispose-remainders-of-deregistered-application
Reason : To ensure that OKM is not sending update-operation-keys to the regarded application's operation-server.
This is modelled so.

Problem :
Incase if the regarded application is one of the TAC and OKM has invariant forwardings for this application.
Then disposal deletes the http-client resulting in non-functioning of the invariant forwardings.

Proposals :
Proposal#1:
For all the application , if it is not regarded successfully , then instead of disposing that application ,
end-subscription shall be initiated to delete the fc-port from the following forwardings,

1. LinkUpdateNotificationCausesOperationKeyUpdates
2. CyclicOperationCausesOperationKeyUpdates

Proposal#2:
If there is any invariant forwardings available for the regarded application , then rollback shall not initiate /v1/dispose-remainders-of-deregistered-application , internally it shall delete the subscription from the following forwardings,

1. LinkUpdateNotificationCausesOperationKeyUpdates
2. CyclicOperationCausesOperationKeyUpdates

[PrathibaJee]

Temporarily this issue is fixed in the PR #334.
Since the provided proposals add complexity , this issue shall be analyzed deeply in the future releases to provide a simple and transparent solution.

Related issue : #309