jira issue type migration quickfix

[valentijnscholten]

Fixes #11821 (for now the easy way).

A proper fix may take some time, this fix will allow users to add extra JIRA Issue Types again via DD_JIRA_EXTRA_ISSUE_TYPES

Usually you shouldn't edit existing migration files. But in this case these "choices" have no effect on the actual database model. Django ORM doesn't propagate these choices to the database. It performs the validation in Python code.

[dryrunsecurity]

DryRun Security Summary

The pull request updates database migration files and Docker test configurations but introduces several security concerns including exposed credentials, debug settings, and validation gaps in the Jira issue type configuration system.

Expand for full summary

This PR modifies database migration files for Jira issue type settings and updates Docker Compose configurations for unit testing.

Security Findings:

1. Potential configuration dependency risks in migration files, with issue types now dynamically configured through settings
2. Database credentials exposed in docker-compose.override.unit_tests.yml with hardcoded username/password (defectdojo/defectdojo)
3. Debug mode set to 'True' in unit tests configuration, potentially exposing sensitive system information
4. Possible configuration manipulation risk due to external issue type configuration
5. No explicit input validation for issue type choices in migration files

Code Analysis

We ran 9 analyzers against 4 files and 0 analyzers had findings. 9 analyzers had no findings.

View PR in the DryRun Dashboard.

[mtesauro]

Approved