Allow submitting non-taxonomy facility type and processing type

[jwalgran]

Overview

We previously returned a validation error to contributors submitting facility types and processing types that did not match the taxonomy. When we began testing with contributors the poor user experience and friction this added to the process made us decide to accept and display non-matching values.

Connects #1703

Demo

Testing Instructions

• Browse http://localhost:8081/api/docs/#!/facilities/facilities_create and authenticate with Token 1d18b962d6f976b0b7e8fcf9fcc39b56cf278051
• Submit the following and verify that it creates a new facility instead of generating an error

{
    "country": "US",
    "name": "API Meta Field Testing",
    "address": "200 Main St Philadelphia PA",
    "number_of_workers": 123,
    "parent_company": "adidas",
    "facility_type_processing_type": "banana|sewing",
	"product_type": ["pants", "suits"]
}

• Browse the new facility and verify that the raw value "banana" appears in both facility type and processing type in addition to the matched taxonomy values for sewing.
• Download a CSV containing the new facility and verify that "banana" appears in both raw and matched columns for both facility type and processing type.

Checklist

• fixup! commits have been squashed
• CI passes after rebase
• CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines

[TaiWilkin]

This looks good! Thanks for updating the tests.
It feels a bit strange to have unmatched values in the facility details alongside matched values. It would be good to have some kind of visual signifier of matched vs unmatched values in the UI. I think that's a design enhancement for the future and not in scope for this task, however.

[jwalgran]

Thanks for the review.

I added a reminder to our cumulative notes document to follow up on the design issue.