deeplake.rename() improvements

[nvoxland-al]

🚀 🚀 Pull Request

Impact

• [X] Optimization
• [X] Breaking change (fix or feature that would cause existing functionality to change)

Description

Previously, deeplake.rename() did a deeplake.deepcopy + delete of the old path. This is very inefficient vs. the storage-level "rename" we can do and this PR changes the method to call the existing dataset.rename() method which already does that.

The rename() method can now also take the simple name to rename to, without re-specifying the whole path

Things to be aware of

That change does mean that you can't use deeplake.rename() to move datasets across storage providers anymore, but that was never the purpose of this method.