Tracking issue of missing functionalities in OpenDAL C binding

Currently the C binding supports...
- [x] write
- [x] read
- [x] delete
- [x] stat
- [x] is_exist
- [x] list

The missing functionalities are.... **(welcome to add up)**
- [ ] async support
- [x] check()
- [x] copy()
- [x] rename()
- [ ] remove() (remove_all(), remove_via())
- [x] reader()
- [x] writer()
- [ ] Future APIs (append (through `write_with(...).append(...))`, etc.)
- This may need some discussions on the implementations since the C does not have such concepts as Future.
- [ ] presign APIs (I think this could be considered later)

Start by reviewing the existing C binding support for write, read, delete, stat, is_exist, and list, then compare it with the unchecked async, remove, Future, and presign APIs. Resolve how Future concepts map to C before choosing an item; done means the selected missing functionality is supported in the C binding and its checklist entry can be marked complete.

Written by the indexing model from the issue text.