Add phone numbers, citizenship, nationality, and email to Residents
Merge remote-tracking branch 'origin/master' into HEAD

* origin/master:
  Add phone numbers, citizenship, nationality, and email to Residents
  Clean up logger calls and unnecessary Dragoman nil provider
  Create a global Dragoman object
  Present a generated form for the resident showing preferred fields
Change the fixtures to fix a couple of broken tests
Add a table for PDF form fields

As an alternative to reading from disk and shelling out to pdftk every time we
inspect a PDF form, we can cache form field names in the database itself.
Create join table for forms and field names, and seed it
Remove redundant ignore
Unit tests no longer touch the sample PDFs or PDF_FORMS

I'd like the tests to continue to work even when the PDF forms are changed, or
moved, or whatever.
Move form_field_hash from Resident to ApplicationController
Remove unused test stubs
Seed resident data with Faker gem
Add previous SSNs to resident
Add race to Resident
Add student/marital status, mailing address, preferred phone to Resident
Go back to SQLite

For now, SQLite's convenience wins out over Postgres's robustness.
Initialize Dragoman by block

Fewer characters, that's all.
Format resident date of birth as mm/dd/yyyy
Add more rules for filling address and race information

Based on existing form field names for Benning Heights.  Some of these form
field names aren't ideal.  For example, the existing race checkboxes aren't
consistently named.
Split the Resident model into Applicant and Person

Housing application forms require information about many different people
associated with a single applicant.  Family members, cohabitants, employers,
landlords, and so forth.

To avoid duplication of many different fields related to the identity of a
single person, Person is its own model.  There's a new model, Applicant, which
represents the person applying for housing.

Applicant has a "self" attribute, referring to the applicant's identity.  It
will require the addition of more person-identifying foreign keys, for family
members and other people involved with the applicant.
Fix seed association between Applicant and Person
Having "self" as a method name in Ruby is a terrible idea