Fixes bug with reason code mapping on not included forms

[ashleybot]

• [x] Only optional forms should be allowed to have NotIncluded selected as a form status
• [x] If NotIncluded is selected then ReasonCode is required when saving the form
• [x] When a form that has NotIncluded as status is edited, the previously selected reason code should also be displayed in the drop down

[ashleybot]

Ok, it definitely was not validating required reason code on Not Required. 🤡

@smiththay I have updated the code, tested again, and these cases should all be true:

• [x] Forms that are not required cannot select "Not included" as a status
• [x] Forms that are optional can select "Not included" and require a reason code to be saved.
• [x] For not included forms, when a reason code is selected, the form is saved successfully. Any data supplied along witht the form is also maintained. For example, they may have recorded some of the B1 vitals, but not all and that's ok if it's not included.

There are opportunities to improve the UX further in this interaction, but that will be saved for a later date.