Don't upsert work item types if not found in the DB
What does this MR do and why?
We will stop upserting work item types if not found on the DB. These types are required to exist before creating issues. These types are seeded into the DB during the install process.
Change behind the rely_on_work_item_type_seeder
feature flag
which is enabled by default. Shipped behind a feature flag
just as a mitigation mechanism in the even we receive reports
of new installs failing like we did in the past. Disabling the
feature flag should fix their problem, but they should really look
into why the install failed to seed the DB properly.
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)