bug: azure behaves differently depending on whether the storage account has hierarchical namespace enabled

[Xuanwo]

When storage account has hierarchical namespace enabled, azure will behave differently on the same endpoint. We need to test and make sure they work as the same.

For example, we can pass the test with hierarchical namespace disabled, but failed while enabled:

---- behavior::test_blocking_stat_with_special_chars ----
test panicked: write must succeed: NotFound (persistent) at write => AzfileError { code: "ParentNotFound", message: "The specified parent path does not exist. RequestId:b2c8148d-a01a-0018-7396-c09d6a000000 Time:2024-06-17T09:09:42.4425331Z" }

Context:
   uri: ***/***/test/8e332949-70f1-4e8d-8fbf-fe8d2ec1b381/?restype=directory
   response: Parts { status: 404, version: HTTP/1.1, headers: {"content-length": "224", "content-type": "application/xml", "server": "Windows-Azure-File/1.0 Microsoft-HTTPAPI/2.0", "x-ms-request-id": "b2c8148d-a01a-0018-7396-c09d6a000000", "x-ms-version": "2022-11-02", "x-ms-error-code": "ParentNotFound", "date": "Mon, 17 Jun 2024 09:09:42 GMT"} }
   service: azfile
   path: 2276e0b2-83f7-4c29-9b02-727e0af9e041 !@#$%^&()_+-=;',.txt

Backtrace:
   0: opendal::types::error::Error::new
             at ./src/types/error.rs:317:24
   1: opendal::services::azfile::error::parse_error::{{closure}}
   

[Xuanwo]

Config related issues, ignore.