feat: Add tracing support via minitrace

[D2Lark]

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/

Summary

Summary about this PR

refer this issue

I want to confirm this function, minitrace has special macros for asynchronous and synchronous functions to implement span functions sent to jaeger via collector, we just want to track read, write, delete these functions?

[Xuanwo]

we just want to track read, write, delete these functions?

Yes, I think it's enough, for now, to only track read, write, delete, stat so far.

[D2Lark]

I move the collector to tests/behaviour file, and add macro to s3 accessor .minitrace_jaeger has been move to dev-dependenices. Should I create anaother tests file for tracing?

[Xuanwo]

Should I create anaother tests file for tracing?

We don't need to test the logic of tracing, they are out of the scope of opendal.

---

BTW, How about adding a new env like OPENDAL_JAEGER_ADDR? We can only set up a collector when we have the OPENDAL_JAEGER_ADDR set.

[D2Lark]

I add this to env
# minitrace OPENDAL_JAEGER_TRACE=on OPENDAL_JAEGER_ADDR=127.0.0.1:6831 OPENDAL_JAEGER_SERVICE_NAME=macro_tracing_test

Curious where to load this env variables. Is it in the tests/behavior or in new function like service/s3::new()

[Xuanwo]

Is it in the tests/behavior or in new function like service/s3::new()

We load env via dotenv: https://github.com/datafuselabs/opendal/blob/6806cb430864475d78a2e64d67facc899150f510/opendal_test/src/services/s3.rs#L31

We will maintian a .env.exmaple as template.

BTW, I think OPENDAL_JAEGER_ADDR is enough, and we don't need to config jaeger service name for testing.

[Xuanwo]

Great, let's merge this PR!