feat: implement new functionality with inserted_at__gte in findings a…

[paabloLC]

Description

Fix: Avoid default date filter when inserted_at or scan__in is present in the URL

🛠 Changes

• Updated logic to skip the default filter[inserted_at__gte] if searchParams contain:
  • Any key related to inserted_at (e.g., filter[inserted_at__gte], filter[inserted_at__lte], filter[inserted_at__date]).
  • filter[scan__in].
• Used Object.entries(searchParams).some(...) to ensure correct detection of date-related filters.
• Ensured no unnecessary default filters are applied when relevant search parameters exist.

✅ Expected Behavior

URL	Applies Default filter[inserted_at__gte]?
/findings	✅ Yes (no inserted_at or scan__in)
/findings?filter[scan__in]=123	❌ No (contains scan__in)
/findings?filter[inserted_at]=2025-02-06	❌ No (contains inserted_at)
/findings?filter[inserted_at__gte]=2025-02-05&filter[scan__in]=123	❌ No (both filters present)

Checklist

• Are there new checks included in this PR? Yes / No
  • If so, do we need to update permissions for the provider? Please review this carefully.
• Review if the code is being covered by tests.
• Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
• Review if backport is needed.
• Review if is needed to change the Readme.md

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.