Bug: Google Drive cloud detection uses English "My Drive" path on non-English Windows

### Description

On a Japanese Windows installation, Google Drive for desktop is mounted as `F:` and its actual root folder is localized as: `F:\マイドライブ`,
Files attempts to access `F:\My Drive`, which does not exist on this localized installation. Startup becomes unresponsive for around one minute. This produces an invalid path warning and Files can remain unresponsive for approximately one minute during startup. On earlier attempts, it remained unresponsive for much longer.

Windows File Explorer can access `F:\マイドライブ` normally. Other local SSD and HDD volumes also respond normally.

This may be related to #16149, but that issue concerned stale Google Drive registry information after Google Drive had been uninstalled. In this case, Google Drive is currently installed and working; the issue appears to be localization of the `My Drive` folder name.

### Steps to reproduce

1. Use Windows with Japanese display language.
2. Install and run Google Drive for desktop in streaming mode.
3. Confirm that the Google Drive virtual drive contains `F:\マイドライブ`.
4. Enable Cloud drives in Files.
5. Enable Continue where you left off.
6. Close and reopen Files.

### Files Version

4.2.0.0, Microsoft Store version

### Windows Version

Windows 11 25H2, build 26200.8894

### User ID

_No response_

### Log

_No response_

Start by tracing the cloud-drive detection and startup restore flow in the Files codebase, focusing on where the Google Drive root path is constructed. Reproduce the Japanese Windows setup described in the issue and verify that the localized root is detected without an invalid-path warning or approximately one minute of startup unresponsiveness.

Written by the indexing model from the issue text.