Misc changes

[DonJayamanne]

• Where possible DirEntry when using readDir instead of converting to PathBuf
• Also review all usages of read_dir Because of this

  /// On Windows this function is cheap to call (no extra system calls
  /// needed), but on Unix platforms this function is the equivalent of
  /// calling `symlink_metadata` on the path.

  See other notes

  /// This function will not traverse symlinks if this entry points at a
  /// symlink. To traverse symlinks use [`fs::metadata`] or [`fs::File::metadata`].

  See here

              for path in readdir.filter_map(Result::ok).map(|e| e.path()) {
                  if let Ok(metadata) = fs::metadata(&path) {

• When dealing with venvs (other than pyenv-venv), never use pyvenv.cfg files to read the versions, As user may have re-created the .venv (or the like) using tools like homebrew python in which case the pyvenv.cfg isn't updated
• Homebrew can be installed in custom paths (use brew --prefix to get the paths)
• Partial versions are never sufficient, i.e. never send versions like 3.10.x as Python extension too does not need this. This means exe and version are always meant to be accurate and fully resolved.
• When accessing medata make note of the fact that symlinks will be resolved and we get metadata for those (hence we might need to get metadata of symlink instead)
• Chanage code from <path>.metadata()..is_dir() to <Path>is_dir, as they are the same

[DonJayamanne]

Homebrew can be installed in custom paths (use brew --prefix to get the paths)

Based on the docs of homebrew, this is discouraged. Will not be adding support for this, as the goal is to focus on the majority case, and the assumption is that majority of the users will not do this (i.e. will not install in custom locations). Even if they do install in a custom location the locators will find them (if they are in path), & will be tagged as unknown which is fine (after all, they're still discovered).