Remove Alexandria as a dependency

[stylewarning]

It is a little awkward that the purported next generation utility platform depends on Alexandria. It should be independent of Alexandria.

We don't depend on Alexandria directly, but we do depend on CL-FAD, which depends on Alexandria.

[stylewarning]

Other dependencies from Quicklisp output:

[package alexandria.0.dev]........................
[package bordeaux-threads]........................
[package cl-fad]..................................
[package path]....................................
[package trivial-garbage].........................
[package impl-specific-gray]......................
[package trivial-gray-streams]....................
[package flexi-streams]...........................
..................................................
..................................................
[package babel-encodings].........................
[package babel]...................................
..................................................
[package cffi-sys]................................
[package cffi]....................................
..................................................
[package cffi-features]...........................
[package cl+ssl]..................................
[package usocket].................................
[package cl-ppcre]................................
..................................................
[package chunga]..................................
[package cl-base64]...............................
[package puri]....................................
[package drakma]..................................

This is a bit heavier than I'd prefer for a utility-acquisition library.

[Shinmera]

If this really does hope to solve the utility library problem, even for light utility usage, it should be absolutely dependency free.

Edit: unless I'm confused on how it's supposed to be used.

[stylewarning]

Well, the utilities themselves (if generated) don't depend on anything.