jira_integration: changes risk acceptance expiration date to a better default

[maxi-bee]

Fixes #13439

[dryrunsecurity]

🔴 Risk threshold exceeded.

This pull request modifies sensitive files related to database migrations and Jira integration (dojo/db_migrations/0245_alter_jira_instance_accepted_mapping_resolution.py, dojo/jira_link/helper.py, and dojo/models.py), triggering configured codepath alerts; review these changes carefully against your .dryrunsecurity.yaml allowed paths/authors before merging.

🔴 Configured Codepaths Edit in dojo/jira_link/helper.py

Vulnerability	Configured Codepaths Edit
Description	Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml.

🔴 Configured Codepaths Edit in dojo/models.py

Vulnerability	Configured Codepaths Edit
Description	Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml.

🔴 Configured Codepaths Edit in dojo/db_migrations/0245_alter_jira_instance_accepted_mapping_resolution.py

Vulnerability	Configured Codepaths Edit
Description	Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml.

We've notified @mtesauro.

---

All finding details can be found in the DryRun Security Dashboard.

[maxi-bee]

That linting rule looks like a suggestion than anything folks, applying the suggestion will make the rest of the similar code look odd. Other than that this looks good to me @valentijnscholten

[valentijnscholten]

That linting rule looks like a suggestion than anything folks, applying the suggestion will make the rest of the similar code look odd. Other than that this looks good to me @valentijnscholten

I made it pass the Ruff linter as that's a requirement.