iter_packages previously considered any directory in a package_path to be a package.
This adds a check that the metadata.path is a file before considering the directory to be a package.

When monas loads its configuration from the top level pyproject.toml, it reads the "packages" field to find local packages via the package_paths property.
iter_packages will scan the package_paths, and check if each one is a directory before turning it into a PyPackage class and yielding it as one of the local monorepo packages.

The PyPackage class will initialize just fine when provided an empty directory. This behavior starts with a check if there is a pyproject.toml file, and if one is not found, it will set its metadata to an empty dict. The SetupCfgMetadata class's match function will return True if provided such an empty dict. This means an empty directory scanned by iter_packages will be initialized as a valid setupcfg project, even in there is no matching setup.cfg file contained in the directory.

I think there may be an argument to preventing this class from initializing at all if there is not a valid setup.cfg file contained in the directory. I wasn't sure if the existing logic was intentional, so I didn't change it.

Instead, I just added a check to iter_packages that verifies that the expected metadata file exists before returning it as a package.