Adding bootstrap, formtastic gems.
Turning on bootstrap and formtastic
Navigating to, and viewing the basic 'new need' form
Creating a new need. Not using Need 'Model' so removing implementation.
Add impact fields to the Needs form.
Convert Need to ActiveModel instance.
Wire up form to new model. Change impact to single choice.
Fix wording for impact levels.
Add field for detailing criteria of a met need.
Pass form data into Need model.

Ensure no blank justification gets into Need model.
Formtastic inserts blank values into checkbox fields.
Preliminary JSON serialization for Need model.
Split 'Needs met' criteria into separate lines.
Submit validated needs to a stub API client class.
Always display the radio and check box options.
Convert 'Needs met' criteria back to string, and display properly.
Use API adapter rather than fake.
Use the hyphenated service name for the need API.
Move webmock into the test group.

Otherwise it prevents real HTTP connections all the time, not just
during test runs. This is bad.
Only make the role, goal and need mandatory.

Even without any of the other information, it's still useful to record
these three fields as a minimal need.
Build up the JSON hash manually.

When we rely on ActiveModel::Serialization's default functionality, it
includes the `errors` and `validation_context` attributes set by the
validation code. The need API rejects these as unknown keys, as it
should.