dump-ecl: Defeat ASDF's magic internal knowledge of itself.
When you load ASDF, it comes with built-in knowledge of itself as a
system, but without details of any source files (or, indeed, any
information about how to do anything with it). When you try to find the
`asdf' system, it does check the filesystem, but does a quick check of
the reported version number against its current version number and skips
loading the full system definition if it's already up-to-date.
This would all be fine in a resident system, because once the system is
loaded, we don't really care much. But ECL isn't a resident system: it
compiles to external files, and this poses a problem. If the initially
loaded ASDF matches the one in the system registry, then we don't have
any source filename details, and `lib-op' does nothing.
Defeat this by locating and loading the system-definition by hand and
stuffing it into ASDF's internal structures before we try to do stuff.
This is, of course, completely terrible.