Cannot open some files when stored in a "cloud" location (iCloud/One/Google Drive, etc.)

I'm using the officials OneDrive (version 23.071.0402.0001) and Google Drive (version 73.0.4.0) macOS apps to sync my cloud files on my Mac. It worked fine for few months, but now I cannot open some files (either Google Drive or One Drive), mostly .docx and .pdf ones but not limited to them. The files are synced to be replicated locally so they are present on the hard drive and they are usable offline. For instance, I'm able to copy a file to the Downloads folder and open it while being offline, but I cannot open it directly from the cloud drive folder. This does not seem to be related to the app used to load the file, the app works fine in other situations. Moreover, I'm unable to open such files with **any** app (for instances Pages for a .docx file). I also checked the privileges of the files and folder and they are normal. What is weird is that I'm able to preview those files with QuickLook (still being offline) but not open them. The app launches but the files never open. I restarted the Mac and the OneDrive and Google apps and switch off then on the sync process but this did not solve the issue. My Mac is up to date, though, it's the last compatible version (macOs Monterey 12.6.4) since it's a MacBook Air early 2015 which is not updatable anymore. I tried to reinstall completely Google Drive and download again all files and the issue is still here. The issue seems to disappear if I disable the local replication of the files (at least in Google Drive), but this defeat the purpose of local replication and its not an option since I need my files offline. For OneDrive the issue disappear if I duplicate the file, but this is not practical neither. I tried to move the un-openable files to iCloud and I get the same issue, I cannot open them. it only works if the files **are not** in a "Cloud" location, i.e. local only. **I was able to replicate the issue on a different machine (MacBook Pro 14" M1 Pro running macOS Ventura) with a different Google account, thus, I strongly believe that the issue is with the File Provider API rather than the files or account.**