Update performance documentation with new understanding of tokio connection

In discussion in https://github.com/maxrjones/zarr-obstore-performance/issues/8 we learned that obstore does actually use threads under the hood. It's single-threaded on the Python side but uses a multi-threaded tokio runtime by default. So the wall time may be improved even when cpu time is not necessarily.