Caching in integrity checker can make integrity checker corrupt workflow data

When running the "Check workflow current step entries" integrity check (WorkflowCurrentStepCheck) a cache is kept around for project-issuetype-status to current step id mapping to speed up the check.

The problem is that the cache is never flushed, so if a project has been migrated to a different workflow scheme (and hence different workflows) the integrity checker starts falsely detecting errors. If the integrity checker is told to fix errors it corrupts the data, such that issues actually end up on the wrong workflow step. When this happens the issue shows the correct status, but the available workflow actions are wrong.

The current solution is to stop and start JIRA. Then run the integrity checker again to actaully fix the problems. Then restart JIRA again to clear the cache.