docs: added section on duckdb reading gcs files

[pieter-factful]

Description of changes

On Zulip I was supported in reading a jsonl file stored on GCS with duckdb. With more people likely te encounter the same issue, it was suggested to add it to the docs. It was suggested to add a new page to the 'how-to' section. The 'input/output' section seemed a good fit.

[kszucs]

In order to fix the lining error pre-commit should be installed, you can find a guide about that at https://ibis-project.org/contribute/03_style

After running the pre-commit the linting errors should be automatically fixed.

[ncclementi]

@pieter-factful looks like you are missing some pre-commits that will take care of the linting if you run them .

Here are some instructions: https://ibis-project.org/contribute/03_style

But in few words, in your conda environment you can do this, that will make sure to run them before you commit, and in most cases it will fix the files, then you can add them again.

$ pip install pre-commit
$ pre-commit install 

[ncclementi]

Whoops, @kszucs beat me for few seconds, I didn't see the comment.

[cpcloud]

Suggested change

	Where `<URL>` is the url provided by GCS. Note that:
	- For private files use the URL with prefix `gs://`
	- For public files you can use the URL with prefix `gcs://`
	Where `<URL>` is the url provided by GCS.

Both gs:// and gcs:// should work regardless of permissions. Is that not the case for you?

[pieter-factful]

I decided to leave out the note altogther. I didn't want to include the specific URL. And figured it unncessary to specifiy the prefix.

As for the access, I checked and yes, looks like all 3 (gs/gcs/storage.googleapis.com all work. Odd, I ran into issues the other day. Maybe mixed up the files: I had both a public and a private version of the file.

[pieter-factful]

@cpcloud @ncclementi @kszucs Looks like all checks passed - thanks for your help!