Additional reworking of list-recipes.

@timsutton,
I think this comes closer to the right approach. The thing that is holding me up a little is what to represent as the file path for an override. Right now it indicates the ParentRecipe's identifier in the output of an override since I think it's indicative of origin, but will show the actual path to the override file (not the parent).  

This would be easy enough to change, but I don't feel strongly either way.
```
$ autopkg list-recipes -i -p

AdobeAcrobatPro9Update.download       com.github.autopkg.download.AdobeAcrobatPro9Update  ~/Library/AutoPkg/RecipeOverrides/AdobeAcrobatPro9Update.download.recipe
AdobeAcrobatPro9Update.munki          com.github.autopkg.munki.AdobeAcrobatPro9Update     ~/Library/AutoPkg/RecipeOverrides/AdobeAcrobatPro9Update.munki.recipe
AdobeAcrobatProXUpdate.download       com.github.autopkg.download.AdobeAcrobatProXUpdate  ~/Library/AutoPkg/Recipe Repos/com.github.autopkg.recipes/AdobeAcrobatPro/AdobeAcrobatProXUpdate.download.recipe
AdobeAcrobatProXUpdate.munki          com.github.autopkg.munki.AdobeAcrobatProXUpdate     ~/Library/AutoPkg/Recipe Repos/com.github.autopkg.recipes/AdobeAcrobatPro/AdobeAcrobatProXUpdate.munki.recipe
```

Also I've introduced a bold strings, in the fashion of 
```
out_string = '\x1b[%sm%s\x1b[m' % ('1;137',out_string)
```

This may be unacceptable for autopkg, due to encoding differences across terminals, but for now a place holder waiting of a better way to demark the parent an override with a matching name refers to.

As always, thanks for your feedback, and letting me contribute,
--Eldon  

Continues #134