Fix #14623: Add created and updated date filters to ApiRiskAcceptance…

[NasorHidar]

Description

This PR resolves Issue #14623.

The risk_acceptance API endpoint previously returned created and updated timestamps but lacked the filter query parameters needed by API consumers. This update modifies the ApiRiskAcceptanceFilter class inside dojo/filters.py to include DateRangeFilter logic for both fields, ensuring they support standard DRF date/time lookups (exact, gt, lt, gte, lte), mirroring the setup used in the findings filtersets.

Test results

Verified the django-filter syntax and dictionary mappings align with existing core model implementations in dojo/filters.py. No existing tests were modified.

[dryrunsecurity]

This pull request includes a sensitive edit to dojo/filters.py detected by the configured codepaths analyzer; the scanner flags it as an error (risk threshold: failing) and notes sensitive file paths and allowed authors can be set in .dryrunsecurity.yaml. The finding is not marked blocking but should be reviewed carefully.

🔴 Configured Codepaths Edit in dojo/filters.py (drs_358dcd66)

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.

---

Comment to provide feedback on these findings.

Report false positive: @dryrunsecurity fp [FINDING ID] [FEEDBACK]
Report low-impact: @dryrunsecurity nit [FINDING ID] [FEEDBACK]

Example: @dryrunsecurity fp drs_90eda195 This code is not user-facing

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

[valentijnscholten]

Could you please rebase against bugfix or dev

[NasorHidar]

Done! Switched the base branch to dev and rebased.