feat: oay fuse frontend support

[oowl]

I would like to know if Opendal has plans to support the FUSE front end for Oay.

FUSE is a great compatibility layer that can convert file system operations from the operating system into user-space API calls. In other words, by leveraging the service capabilities of Opendal's ecosystem, I can use this FUSE layer to access a wide range of cloud drives and object storage through the file API of the operating system.

For example:
https://github.com/astrada/google-drive-ocamlfuse
https://github.com/s3fs-fuse/s3fs-fuse

[Xuanwo]

The FUSE's power & performance could be very limited:

• 4K Read will very slow (especially on object storage services like s3)
• Only sequential writing is supported. Random writing without a in-memory buffer is not possible.

[Xuanwo]

Maybe we start with a read-only fuse first?

[oowl]

The FUSE's power & performance could be very limited:

* 4K Read will very slow (especially on object storage services like s3)

* Only sequential writing is supported. Random writing without a in-memory buffer is not possible.

I believe these limitations do not affect our functionality. These limitations only result in some performance issues, which seem to not be a problem in certain scenarios where the backend is S3.

Maybe we start with a read-only fuse first?

Yeah， I can try it from fuse read-only support.

[oowl]

It seems that https://github.com/cberner/fuser is a good choice of fuse crates that are only active fuse implementable.

[Xuanwo]

Work tracked at #3782