Make the BerksfileNotFound exception less confusing

As of now, if reading `metadata.rb` throws an ENOENT (like if you're reading a nonexistent README.md to generate a description D:), berkshelf will give you a possibly incorrect error message.