Fix printing tensor bug - regression introduced in #6444

[saurabheights]

Type

• Bug fix (non-breaking change which fixes an issue): Fixes #https://github.com/isl-org/Open3D/pull/6444/files#r1430396718
• New feature (non-breaking change which adds functionality). Resolves #
• Breaking change (fix or feature that would cause existing functionality to not work as expected) Resolves #

Motivation and Context

My apologies for adding the regression in printing of cuda tensor. I recently got the cuda build working, thus detected this regression late. I have tested the bug.

Checklist:

• I have run python util/check_style.py --apply to apply Open3D code style
  to my code.
• This PR changes Open3D behavior or adds new functionality.
  • Both C++ (Doxygen) and Python (Sphinx / Google style) documentation is
    updated accordingly.
  • I have added or updated C++ and / or Python unit tests OR included test
    results (e.g. screenshots or numbers) here.
• I will follow up and update the code if CI fails.
• For fork PRs, I have selected Allow edits from maintainers.

Description

The earlier PR #6444 added a bug where suffix for cuda tensor is printed when it is moved to CPU and then again when it is in GPU.

o3d.core.Tensor.eye(n=4, dtype=o3d.core.Dtype.Float64, device=o3d.core.Device('cuda:0'))
[[1 0 0 0],
 [0 1 0 0],
 [0 0 1 0],
 [0 0 0 1]]
Tensor[shape={4, 4}, stride={4, 1}, Float64, CPU:0, 0x561c38e195d0]
Tensor[shape={4, 4}, stride={4, 1}, Float64, CUDA:0, 0x302000000]

This is fixed with test below.

Again, my apologies. This being added to v0.18 just makes it worse.

[ssheorey]

Thanks @saurabheights !
CI failure is unrelated to PR.