NSLCM statuses are presented as strings, rather than JSONs

Last OSL’s release included a new feature that enabled to list all NSLCM status of a service. This was made possible with the development of backend business logic on the osl.tmf.api module and the some frontend development on the osl.tmf.web module. The listing of all NSLCM statuses should be presented as a JSON array, where each item is a NSLCM status collected from the NFVO (in the form of a JSON payload). However, this is not what is happening, as NSLCM statuses are presented as strings, rather than JSONs (see image below).