✨ [Frontend] Enh: Adapt to paginated navigation and to new model

[odeimaiz]

What do these changes do?

In this PR the frontend stops using the following endpoints:

• /storage/locations/{locationId}/datasets/{datasetId}/metadata
• /storage/locations/0/files/metadata?uuid_filter={nodeId}

which were replaced by:

• /storage/locations/{locationId}/paths
• /storage/locations/{locationId}/paths?file_filter={path}

The strategy for populating the files trees was updated to lazy-load the content of a folder when necessary. Before we would fetch the content of a study with all its subfolders when accessing the first level of a study.

This PR adapts also the new response model, but we still don't take full advantage of the pagination (this will come in a follow up PR).

Related issue/s

• related to Frontend: Use paginated storage API #7278
• follows ✨Storage: new paths entrypoint with pagination #7200
• related to UI/UX for Data Handling (Feb.) osparc-issues#1635

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud