logging fee account presence true or false
apply logstuff changes to production environment
fix bug which caused production to write to logstash_development.log
Getting prod remote tests to pass

Since most of the test were in dev, and we use the feature tests in
order to test prod, some of the data used for faking out the responses
was wrong. This commit aims at fixing that.
Handle production remote test problems

These changes make remote tests in production pass. Dirty
workaround. I'd love to hear better ways of handling this.
Enable logstash for testing
Merge branch 'master' into fee_acct_num_recorder

* master:
  removed duplicate claimant contact reference field
  updated checklist on pdf
  Updated the PDF fields tests
remove temp TODO file
Merge pull request #541 from ministryofjustice/prod-tests

Prod tests passing
Merge branch 'master' into fee_acct_num_recorder

* master:
  Handle production remote test problems
  Getting prod remote tests to pass
Merge pull request #542 from ministryofjustice/fee_acct_num_recorder

Fee acct num recorder
Upgraded courtfinder-gem from 0.0.5 to 0.0.6
Merge pull request #543 from ministryofjustice/courtfinder-gem-upgrade

Upgraded courtfinder-gem from 0.0.5 to 0.0.6
record IP address and don't record twice for one session
Merge pull request #544 from ministryofjustice/fee_account_num_2

record IP address and don't record twice for one session
Pickup correct remote ip
Merge pull request #545 from ministryofjustice/fee_account_num_2

Pickup correct remote ip
Whitespace change to force pull request to re-merge and re-test
Merge pull request #546 from ministryofjustice/fee_account_num_2

Whitespace change to force pull request to re-merge and re-test
Merge branch 'master' into courtfinder-error-links