Add initial code to add columns for form fields

Issue #4
Expand support for adding fusion table columns for custom user fields in
a form.
This will determine the column name and column type based on the form
field itself.
Not much special handling for various fields yet, but the scaffolding is
in place.
Add ! to method name for clarity
Extract field key/name method to another class

Issue #4
Pull out the method for getting a form's key-name mapping for the fields
to its own class.
Makes FormFields more single-responsibility.
Make conditional more readable
Make field key-name mapping more readable
Merge rspec examples

Close #7.
Issue #4.
Break FormFields classes out into files

Issue #4.
Pull all the classes that had been in FormFields into their own files.
Make form fields classes kick off form fields spec
Fix indenting in Guardfile
Make the sinatra app modular

Allows us to start the app with Rack.
Also add in lines to use Bundler.
Use fusion_tables fork

Use a branch of kyletolle's fork of fusion_tables so we can take
advantage of the escaped single quotes in column names.
This require's bundler to be required, which was added in the previous
commit.
Add gem versions to Gemfile
Remove guard block from Guardfile

This functionality seems to be provided by guard without this block.
Add guard-bundler

Set up Gemfile and Guardfile to use guard-bundler.
Tweak guardfile

Remove a warning message when running guard.
Make tests work with modular sinatra app

Pull common config code into its own file to be used by rack and rspec.
Update README with changes to port info
Move environment var config to config folder

Also rename it so it's more apparent what it is.
Make guard watch config files
Fix busted rackup config