directory.resourcePath and directory.friendlyName are empty strings in the response of MFTTransferService.resourceMetada method.

Not sure if this is the intended behavior of `MFTTransferService.resourceMetada` method, please let me know if it is.
When I send a request to get the resource meta-data for a particular directory, I'd expect to get the **resourcePath** and/or **friendlyName** of that directory in the response as well.

But here, the resourcePath and friendlyName both are **empty strings**.

I needed this data to maintain a tree structure for the folders which the user has visited inside the airavata mft local user interface. It will also be helpful to cache it and prevent redundant requests when the user clicks on a folder, goes back to the parent folder and then clicks on the same folder again within a few seconds.


One more example -


Start by locating the Java implementation of MFTTransferService.resourceMetada and the response type it returns. Reproduce the directory metadata request and trace how resourcePath and friendlyName are populated. Done means the response contains the requested directory's expected path and/or friendly name, with tests covering the behavior.

Written by the indexing model from the issue text.