fix(services/dropbox): fix dropbox test failed

[zjregee]

fix: #4314

[oowl]

Thanks!

[Xuanwo]

It's a bit odd that dropbox returns a failure without an error. Do you know the actual response from dropbox services?

[zjregee]

Sorry for overlooking a potential issue.

Yes, it returns an error format that the current DropboxErrorResponse cannot parse. We should modify DropboxErrorResponse to support the new error format.

Due to the 1password settings, I cannot completely reproduce the test in CI. The following are the results of testing using a personal account.

When an error occurs during the stat call, Dropbox returns an error like this:

{
    "error_summary": "path/not_found/",
    "error": {
        ".tag": "path",
        "path": {
            ".tag": "not_found"
        }
    }
}

When an error occurs during batch call, Dropbox returns an error like this (causing an expect error):

{
    ".tag": "complete",
    "entries": [
        {
            ".tag": "failure",
            "failure": {
                ".tag": "path_lookup",
                "path_lookup": {
                    ".tag": "not_found"
                }
            }
        }
    ]
}

[Xuanwo]

Got it. Seems we need to parse the error response from dropbox correctly.

[zjregee]

I added DropboxDeleteBatchFailureResponse to parse errors during batch deletion.

When dropbox returns the following error.

{
    ".tag": "failure",
    "failure": {
        ".tag": "path_lookup",
        "path_lookup": {
            ".tag": "not_found",
        }
    }
}

OpenDAL will return such an error message.

Error: Unexpected (permanent) at delete, context: { service: dropbox, path:  } => delete failed with error path_lookup not_found

[Xuanwo]

OpenDAL will return such an error message.

Thank you for looking into this. This is precisely the situation I wanted to address: we can ignore the "not_found" error when deleting.

[zjregee]

I'm very sorry for deleting this PR due to my mistake. I will initiate a new PR later.