Standardize path handling throughout the code base

[GeigerJ2]

As discussed with @edan-bainglass.

In PR #6255, an inconsistency in the type handling of the filepath_executable of PortableCode was identified by the introduction of pydantic (see here for reference).

Looking throughout the code base, we have two different type aliases for path-like types:

aiida-core/src/aiida/transports/transport.py

Line 27 in 660fec7

TransportPath = Union[str, Path, PurePosixPath]

aiida-core/src/aiida/repository/repository.py

Line 15 in 660fec7

FilePath = Union[str, pathlib.PurePath]

FilePath also here:

aiida-core/src/aiida/orm/nodes/data/folder.py

Line 26 in 660fec7

FilePath = t.Union[str, pathlib.PurePath]

aiida-core/src/aiida/orm/nodes/data/singlefile.py

Line 25 in 660fec7

FilePath = t.Union[str, pathlib.PurePath]

As well as standard type hints for paths, and combinations of the two:

aiida-core/src/aiida/repository/repository.py

Line 483 in 660fec7

def copy_tree(self, target: Union[str, pathlib.Path], path: Optional[FilePath] = None) -> None:

While I wouldn't deem this super high priority, it might be useful to standardize those path-like annotations if possible, or at least put them in a dedicated module, e.g., aiida/common/types.py. Also, many (probably older) parts of the codebase use os.path (this is especially prevalent in the transport plugins), where we could also consider switching to pathlib at some point.

[ayushjariyal]

Hi @GeigerJ2 , I'd like to work on this issue.
Please let me know if there are any specific guidelines you'd like me to follow while making these changes.

Thanks!

[ayushjariyal]

@GeigerJ2 , I’ve opened a PR addressing this issue. Could you please review it?