Handle network errors during load container operation

[bhavin121]

Description

This pull request addresses the issue of unhandled generic network errors during the document loading phase in the Fluid client.

Issue

When a genericNetworkError occurs during the attach phase while creating a new document, it is retried based on the canRetry flag. However, if the same genericNetworkError occurs while loading an existing document, no retry is attempted, and the user receives the exception.

• The attach method in container.ts wraps the call to serviceFactory.createContainer in runWithRetry, which handles retries in case of an exception.
• The load method in container.ts directly calls serviceFactory.createDocumentService without wrapping it in runWithRetry, leading to unhandled exceptions.

Changes Made

• Wrapped the call to serviceProvider() in runWithRetry within the createDocumentService method in container.ts.
• Ensured that the retry logic mirrors the strategy employed during the attach phase (As we are using the same runWithRetry method that is used in the attach function).

Impact

Implementing a retry mechanism during the document loading phase will significantly enhance the Fluid client’s resilience to network errors, providing a smoother and more reliable user experience.

This PR addresses #24114

[tylerbutler]

@vladsud Could you take a look at this or recommend someone to? Thanks!