[MJ-775] A Partner library

Introduces the PartnerLibrary model as well as tools to manage it:

* `python manage.py update_partner_library` - parses HTML returned from the OFCCP directory after some trickery (thanks @almathew) and converts the result into PartnerLibrary records, discarding duplicates (as determined by contact name, city, and state).
* `mypartners.helpers.get_library_as_html` - returns a string representing the html returned by the fore-mentioned trickery
* `mypartners.helpers.get_library_partners` - generator that returns a lightweight object representing a partner retrieved from the OFCCP souce mentioned above. This function drives the `manage.py` command. This can either parse an HTML text file, or retrieve HTML if you have a working connection.
* `mypartners`
The PartnerLibrary model omits the job category fields since it was determined that they weren't necessary for my use case. However, the helper functions retrieve that data, so should we find a use for them (such as tags), it would be a simple matter of adding a migration along with `BooleanField`s to represent them.

@galitskyd has done some amazing work on the UI, completely overhauling the PRM overview page, as well as integrating the partner library into them. Our presentation Monday should go over most of those changes. For any other details regarding that, I'll let him comment, as I'm sure I'll miss some of the nuances. 

Yeah. First, middle and last name were originally distinct fields, which is why that comment is there in `__unicode__`. I moved the code to tasks and didn't bother with updating/moving the comment. 

On another note, I'm apparently not getting notifications when my PRs are being commented on, hence the delay in responding. Sorry abut that.