Fix processing_type_facility_type_unmatched

[TaiWilkin]

Overview

The warning we set up in the processing_type_facility_type_unmatched
report to let us know about certain invalid values
in the system was triggering all the time, and not just when it should
be, due to an indentation issue.

Connects https://rollbar.com/OpenApparelRegistry/OpenApparelRegistry/items/1576/?item_page=0&#similar-items

Testing Instructions

• On develop, add a debugger or a print statement at the Rollbar error in processing_type_facility_type_unmatched() and ensure you have at least one unmatched processing_type value. Ensure the unmatched value has been added to the system properly.
• Open the processing_type_facility_type_unmatched report and see that the error is triggered incorrectly.
• Repeat the above steps on this branch and see that the error is not triggered.

Checklist

• fixup! commits have been squashed
• CI passes after rebase
• CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
• This PR is targeted at the correct branch (develop vs. ogr/develop)
• If this PR applies to both OAR and OGR a companion PR has been created

[jwalgran]

I confirmed the error and the fix, and had forgotten that Python for statements could have an else.

[TaiWilkin]

Thank you for reviewing!
I had almost forgotten the new OGR workflow, but I've added a PR for the OGR branch. I'll hold off on merging this until that is reviewed, per the order of operations in the Readme.