If current-application http-c is updated during execution of /v1/update-client , ltp change is not updated to ALT

[ManasaBM1]

Issue Description:

When we execute /v1/update-client service in a combination where future-application http-c details are not present , then current application http-c is set with future-application-name and future-application-release-number. In this scenario /v1/update-ltp is not being sent to ALT.

Priority:Low;
AffectedFlow:None;

[PrathibaJee]

In the TinyApplicationController , this will not be a problem , because before receiving a update-client , a regard-application will be received and a ltp client for the new release will be included in the configuration file.
But , for the applications that didnt subscribed for approval-notification , they will have only a single instance of the application client for which they will receive a update-client. when they receive update-client , then the forwarding to ALT will not happen.

For example :
For this request body ,

{
  "current-application-name": "RegistryOffice",
  "current-release-number": "2.0.1",
  "future-application-name": "RegistryOffice",
  "future-release-number": "5.8.3",
  "future-protocol": "HTTP",
  "future-address": {
    "ip-address": {
      "ipv-4-address": "1.2.1.1"
    }
  },
  "future-port": 3000
}

In the loadfile , we have a ltp instance , that matches the current-application-name + current-release-number
So , the matched ltp , will be updated from "2.0.1" to "5.8.3"
After this a update ltp will not be sent if the application didnt have the future release ltp instances.