Inconsistent database state for Issue Type Scheme on Update and Remove

Summary

If you update the issue type scheme while removing an issue type you can get into a state where there is an option in the optionset that doesn't exist. This database corruption was the cause of JRA-45161. Fixing this would be removing another way to get into this state.

Steps to Reproduce

1. Get an instance with an Issue Type Scheme with a set of Issue Types
2. Current Option Set: [1, 2, 3], In the UI I change it to [1, 4, 2, 3]. Where these numbers represent Issue Types.
3. During this processing, delete one of the Issue Types
4. Check the database table optionconfiguration and there could be a possible row with an optionid that no longer exists.
5. Until JRA-45161 is fixed this results in NPE in the UI.

Expected Results

Can create Issues like usual and the database table optionconfiguration should only have valid options.

Actual Results

Cannot create Issues or view workflows because of NPE and the database table optionconfiguration contains invalid options.

Workaround

This can be fixed by following the workaround in NullPointerException when creating issue, editing issue, move issue, accessing the Screen tab from the Project.