Expand the payload sent for studio table resources to make adding to DataPanel easier

**Problem**: Right now we receive only the following information in the payload per row of the table:

```
{
"s": {
"type": "uri",
"value": "https://dev.nise.bbp.epfl.ch/nexus/v1/projects/bbp-users/dinika"
},
"self": {
"type": "uri",
"value": "https://dev.nise.bbp.epfl.ch/nexus/v1/projects/bbp-users/dinika"
}
}
```
This information is not enough to add a row to data-panel, so we do another (upto 2 requests) per row selected

1. Get information such as, `@id` ,`distribution`, `createdAt`, `name` etc. A sample of what we receive is as follows
2. If the `@id` returned by the response to the request above is of "curie" format, we make another request to get expanded id. (To be seen, if we can only do this request instead of the first one).

**Proposal**
Get the following extra information in the original request that returns all rows for studio table row:

- @id (expanded one, not just a curie)
- name
- project
- self
- description
- createdAt
- updatedAt
- @type
- distribution

Start by tracing the original request that returns all rows for studio table resources, then inspect the follow-up requests used to retrieve @id, distribution, createdAt, name, and related fields. Done means the original payload includes the proposed fields with an expanded @id, reducing or removing the per-row follow-up requests.

Written by the indexing model from the issue text.