The issue fixed is that most Lisps don't like
*default-pathname-defaults* being a logical-pathname.
Added a test for logical-pathname functionality;
it all works on CCL, and works better on other Lisps after the fix,
but there are still logical-pathname issues on SBCL, CLISP and more.
Also, a package cleanup of our test suite.

Also, use coerce-pathname in asdf-ecl and deprecate merge-component-name-type.

Add janderson's pathname test script to our test suite.

Try to play well with LOGICAL-PATHNAMEs.
Introduce utility MERGE-PATHNAMES* that tries to do the Right Thing(tm).

Simplify test scripts.

perl -pi.bak -e 's|"../asdf"|\(compile-file-pathname "../asdf"\)|;' *.script

Found that the current load recipe (load "../asdf") in the test
scripts was brittle, because the presence of asdf.fasl was obscured
if there was an "asdf/" directory in ..  Unfortunately, the result
of makeinfo --html asdf.texinfo created just such a directory!
fe[nl]ix kindly provided a pointer to compile-file-pathname that
solved the problem.

Some glue that won't affect too many people but that lets ASDF cleanly
hook the extensible PROVIDE/REQUIRE mechanism in upcoming SBCL 0.7.13

Fix wild-modules to not object when we call (setf (module-components))
on a new or about-to-be-reinitialised module.  We need to be able to
do this to get the weeds out, so it should be legal

wild-pathname-based modules for asdf.
(:wild-module "name" :pathname "foo/*.bar" :component-class 'bar-file), e.g.