ENH: Allow .resolve() with CloudPaths

[remi-braun]

Hello,

In order to simplify the code and unify the API, would it be possible to allow the .resolve() function to CloudPaths, even if this function does nothing ?

To go from:

path = AnyPath(path)
if not isinstance(path, CloudPath):
   path = path.resolve()

to

path = AnyPath(path).resolve()

Thanks a lot

[pjbull]

We already have a _resolve method that we use to make sure there are no relative paths in the key part of the CloudPath. Seems reasonable to expose this functionality in the .resolve method:

cloudpathlib/cloudpathlib/cloudpath.py

Lines 846 to 868 in 25ff783

	# The function resolve is not available on Pure paths because it removes relative
	# paths and symlinks. We _just_ want the relative path resolution for
	# cloud paths, so the other logic is removed. Also, we can assume that
	# cloud paths are absolute.
	#
	# Based on resolve from pathlib:
	# https://github.com/python/cpython/blob/3.8/Lib/pathlib.py#L316-L359
	def _resolve(path: PurePosixPath) -> str:
	sep = "/"
	# rebuild path from parts
	newpath = ""
	for name in str(path).split(sep):
	if not name or name == ".":
	# current dir, nothing to add
	continue
	if name == "..":
	# parent dir, drop right-most part
	newpath, _, _ = newpath.rpartition(sep)
	continue
	newpath = newpath + sep + name
	return newpath or sep

The tricky part will be to get all the test cases included for this kind of functionality. (E.g., path that ends in .., .. that goes above the bucket level, etc.)

[remi-braun]

For sure these moot points can be tricky, however do they really happen when handling cloud paths ? (especially since the relative_to function is not implemented)
Maybe just add a warning in the documentation first, and deal with this if the users are asking 😛

[pjbull]

Added as a no-op for API consistency in #230