Add validation to prohibit users to order mip/raredisease cases without an affected individual

[karlnyr]

As a production user,
I want a validation that prohibits customers from placing order of MIP/raredisease analyses without an affected individual,
So that we will do the proper ranking of variants and thus reduce the amount of variants uploaded to Scout.

Work impact

Answer the following questions:

• Is there currently a workaround for this issue? If so, what is it?
  • None
• How much time would be saved by implementing this feature on a weekly basis?
  • None
• How many users are affected by this issue?
  • Production, if the Scout database would fill up we would have large issues at hand
• Are customers affected by this issue?
  • Yes, currently customers can place orders of a mip/raredisease case without an affected individual and thus have a lot of variants to filter through in Scout as well.

Acceptance Criteria

• When placing an order of a new mip/raredisease case the user should be able to upload an json that may have the phenotype status "unknown" and thus be prompted to change this status to either "affected" or "unaffected"
• The phenotypic status options should only be "affected" or "unaffected" for mip/raredisease individuals
• Add a validation that fails if a case does not contain an affected individual
  • This should only be triggered when the case is saved, so that the customer could add the unaffected individuals first
• When placing an order for an existing case, and the case does not have an affected individual, inform the customer to create a new case instead of using the old one. Meaning, that we would not allow those cases to be re-analysed as they are.

Notes

• Additional information.
• Dependencies.
• Related user stories.