bug: When using gdrive as the schema, create_dir is not working properly

[arianrhodsandlot]

Describe the bug

When calling create_dir with gdrive as the schema, the directory is not created with an expected name.
I was using the latest Node.js bindings.

Steps to Reproduce

import { Operator } from 'opendal'

const op = new Operator('gdrive', { access_token: '****' })

// a directory with name 'a/' created since Google Drive treats '/' as a valid character for file name
await op.createDir('a/')

// an error occurred:
// Error: NotADirectory (permanent) at create_dir, context: { service: gdrive, path: a } => the path trying to create should end with `/`
await op.createDir('a')

There seems to be no way to create a directory whose name does not contain a trailing slash.

Expected Behavior

While calling await op.createDir('a/'), a directory named 'a' rather than 'a/' should be created

Additional Context

No response

Are you willing to submit a PR to fix this bug?

• Yes, I would like to submit a PR.

[Xuanwo]

I'm guessing we need to trim the / after name:

opendal/core/src/services/gdrive/core.rs

Lines 396 to 405 in 410f7ed

	async fn create_dir(&self, parent_id: &str, name: &str) -> Result<String> {
	let url = "https://www.googleapis.com/drive/v3/files";
	let content = serde_json::to_vec(&json!({
	"name": name,
	"mimeType": "application/vnd.google-apps.folder",
	// If the parent is not provided, the folder will be created in the root folder.
	"parents": [parent_id],
	}))
	.map_err(new_json_serialize_error)?;

[arianrhodsandlot]

It seems create_dir isn't the only method not working as expected with gdrive, a majority of the methods related to gdrive seem to have some issues with the slashes as well. Examples:

code(Node.js)	result	note
await op.write('/a/b/c.txt', 'hello!')		the names of parents should be 'a' and 'b' rather than 'a/' and 'b/'
await op.list('/a/')	[]	should be ['b2', 'b1', 'b']
await op.read('/a/b/c.txt')	[Error: NotFound (permanent) at read, context: { service: gdrive, path: a/b/c.txt, range: 0- } => path not found: a/b/c.txt]	should return the content of the file