fix(api): add created/updated date filters to risk_acceptance endpoint

[SAY-5]

Summary

Closes #14623.

The risk_acceptance API returns created and updated timestamps in its responses but ApiRiskAcceptanceFilter did not expose either as a query parameter, while the matching findings, products, and assets filters all do (see ApiProductFilter, ApiFindingFilter for the same pattern). Clients had no way to scope listings by acceptance date.

Change

Add DateRangeFilter(created) and DateRangeFilter(updated) to ApiRiskAcceptanceFilter and expose both fields in the existing OrderingFilter, matching the convention used by the sibling resources.

class ApiRiskAcceptanceFilter(DojoFilter):
    created = DateRangeFilter()
    updated = DateRangeFilter()

    o = OrderingFilter(
        fields=(
            ("name", "name"),
            ("created", "created"),
            ("updated", "updated"),
        ),
    )
    ...

Risk_Acceptance.created (auto_now_add) and Risk_Acceptance.updated (auto_now) already exist on the model (dojo/models.py L3976–3977) so no migration is needed.

Test plan

• python -c 'import ast; ast.parse(open("dojo/filters.py").read())' — file parses
• Confirm OpenAPI schema for /api/v2/risk_acceptance/ lists created, updated, and o query parameters
• Manual: GET /api/v2/risk_acceptance/?created=week returns last week's acceptances; GET /api/v2/risk_acceptance/?o=-updated sorts by most-recently-updated first

[dryrunsecurity]

This pull request includes a sensitive edit in dojo/filters.py that was flagged by the configured codepaths policy. The scanner indicates this file is treated as sensitive and may require special authorization or configuration in .dryrunsecurity.yaml.

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

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.

[mtesauro]

@SAY-5 Please make your PR against the DEV branch - we don't accept PRs against master.

For more info, see https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md#submitting-pull-requests