Slow or unreachable federated shares shouldn't slow down NC so much

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
When (especially larger) federated shares from other NC instances are within a directory, loading of the directory content will not terminate before the shared directory is fetched (probably mainly metadata, like size, modified date) as well. This can lead to long loading times, or, in the worst case, timeouts and a blank page.

Describe the solution you'd like
I'd propose the following solution:
Shares could be displayed without metadata. Metadata could be loaded in a subsequent, non-blocking request.

Additional context
I'm currently on NC 22.2.2

No files or tests are named. Start by reproducing a directory containing a large or unreachable federated share and trace the directory-loading request to identify where remote metadata blocks completion. Done means the directory can render without waiting for that metadata, with the metadata fetched afterward without blocking the initial request.