Changed the error message received when specifying an invalid target in ...

...a BUILD file to actually be helpful.

Previously pants just choked with a ValueError stating that the spec was not found in the BUILD file. Now it actually lists valid specs that are contained in the build file, so that the user can recover easily without inspecting the BUILD file's contents. It also searches through 'sibling' BUILD files in the same directory, if they exist.

See issue: https://github.com/pantsbuild/pants/issues/224
nit: for clarity I would rename 'addr' to contain the word 'target', 'proxy', or 'target_proxy'