[Data] Handle logs from tensor extensions

[bveeramani]

Why are these changes needed?

Tensor extensions are implemented in the air subpackage, and Ray Data doesn't handle logs from that package by default

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[raulchen]

any downside of including the whole ray.air?

[bveeramani]

Hmm...haven't dug through all of the air code, but would want to avoid writing non-Data logs to ray-data.log (e.g., if there's some Train stuff)