Don't fail so loudly if default work item type is invalid
What does this MR do and why?
We now raise a loud error if a default work item type is not found in the DB, explaining users that they should make sure the types are seeded into the DB.
We should not fails so loudly if the provided type is not expected to be found in the DB, even if the seeds were run correctly. Then, we return nil instead and let calling methods handle the null value as before
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #459904 (closed)