Use the generated complete dependency spec when initializing the perl env

SInce we're generating the complete dependency spec during the depends
command, use it in subsequent commands rather than triggering a
re-expansion from scratch.
Corrected the logis to search for major[.minor] efsdeploy rules

The major and possible minor version specific efsdeploy rules search
was totally broken.
Utility to search the depends.conf files

Crude, simply tool to search for entries in the depends.conf files.
I'm using this to figure out which releases end up depending on a
given project directly.  Since we collapse everything into the
complete spec, we lose that information (direct vs indirect).
Major, but subtle, changes to how recommends and suggests are handled

In an attempt to get maximum test suite coverage while building
dependency tree with cpan2efs, we usd to try to build the recommends
and even the suggests dependencies, but this has proven to create a
seeminly infinite number of circular dependencies.  It also ends up
with a few runtime dependencies on test modules that aren't necessary,
due to some poorly written specs (those case be fixed).

Now, suggestrs are completely ignored, and recommends are treated as
optional dependencies, and will be used if they are found.  cpan2efs
will NOT try to build anything other that required dependencies, so we
may have to go back and rebuild specific distros to get the extra test
suite coverage if we want it.
Better hack for guessing is a distro is in the core

The is_core method returns true is any of the modules are found in the
core.  This is only used to workaround circular dependencies in cpan2efs.
The modulenames method return an ARRAYREF not an ARRAY