🚧 Change Dynimoid logging level to :info

[huwd]

Trello: https://trello.com/c/99xm7mlq/86-ensure-sensitive-data-doesnt-go-to-logit-splunk

DRAFT PENDING TEST ON STAGING
Replaced by: #168

Test

• Get this on staging
• Noodle around
  • Normal browse behaviour
  • Cause an error
  • Submit a stand-in for PII
  • Cause validation error
• Logs should have No PII
• Logs should have validation errors
• Logs should have errors
• check the logs since deploy

What

tweak the logging levels in production to prevent PII getting in, but ensure we still get useful logs on validation attempts

Why

Keep cyber happy, keep debugging devs happy.

[bilbof]

Looks good 👍

[huwd]

Made a paralell one for the vulnerable people form:
Sean noted - alphagov/govuk-coronavirus-vulnerable-people-form#172

Do turns out logs can have PII in them cry - We ended up having reduce the log level #141. I think Dynamoid is sharing the default Rails logger - so we are suppressing all Rails log with setting. Maybe need to make a separate logger? Think we need info level for rails as validation errors probably aren't "application errors".

[huwd]

This should go on hold or be closed depending on the outcome of this PR:
alphagov/govuk-coronavirus-vulnerable-people-form#205

I suggest we get the response right there and then mirror it from the vulnerable people app to this one