feat: improve observability of BytesReader and DirStreamer

[ClSlaid]

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

Why are so many files edited?

My code format was a mess so I ran a complete format...

Summary

By wrapping BytesReader and DirStreamer in a way like layers in v0.13.0, a leap of observability is done.

1. logging with LoggingReader and LoggingStreamer, when Accessor::read, Accessor::write, Accessor::list and Accessor::write_multipart()
2. tracing with TracingReader and TracingStreamer, when Accessor::read, Accessor::write, Accessor::list and Accessor::write_multipart()
3. metrics with MetricReader, when Accessor::read, Accessor::write and Accessor::write_multipart()

Need discussion

• The span of tracing
• What to record in Metric

Related issue

• fixes refactor: replace redundant log macros with logging layer #589
• fixes Tracking Issues of OpenDAL Observability #527

[Xuanwo]

My code format was a mess so I ran a complete format...

rustfmt confirmed that we get the same format (you will find the check didn't pass)

You can try this way:

• Uncomment the rustfmt.toml, run cargo +nightly fmt
• Comment the rustfmt.toml back, run cargo fmt

[ClSlaid]

rustfmt confirmed that we get the same format (you will find the check didn't pass)

By "complete format" I mean uncommeting all lines in rustfmt.toml and running cargo fmt on nightly channel. Because I was too lazy to take a hundred imported modules out from curly brackets and sort them manually, and rustfmt will do nothing to imports by default.

Sadly, the default rustfmt style is not the same as databend. I should have checked before pushing. :(

[Xuanwo]

Sadly, the default rustfmt style is not the same as databend.

Because OpenDAL should be run on stable rust, we can't use the same rustfmt.toml as databend.

I should have checked before pushing. :(

Don't worry. CI is always here until you make them happy.

[Xuanwo]

I should have checked before pushing. :(

Some more comments about statements like those

Don't worry about revokable errors: Everything is OK. It's just a simple mistake and is detected by CI. No one should be blamed here, especially in open-source projects like OpenDAL. I don't care about any mistakes that could be detected by CI, like styling and formatting.

But I do care:

• The time and effort that you put into this PR.
• The code quality you represent includes naming, comments, API design, and so on.

Let's focus on the essential part and let our CI worry about those slight mistakes.

[Xuanwo]

LGTM now!

Thanks for your patience~