feat(dynamic_filters): add dynamic filters system

[AdriiiPRodri]

Context

In this PR I have added the endpoint to get the filters dynamically depending on the findings of a date.

Description

Using the specified date, all the findings of that date and the services and regions associated with them are extracted.

{
    "data": {
        "type": "findings-services-regions",
        "id": null,
        "attributes": {
            "services": [
                "accessanalyzer",
                "account"
            ],
            "regions": [
                "ap-northeast-1",
                "ap-northeast-2",
                "ap-northeast-3",
                "ap-south-1",
                "ap-southeast-1",
                "ap-southeast-2",
                "ca-central-1",
                "eu-central-1",
                "eu-central-2",
                "eu-north-1",
                "eu-south-2",
                "eu-west-1",
                "eu-west-2",
                "eu-west-3",
                "sa-east-1",
                "us-east-1",
                "us-east-2",
                "us-west-1",
                "us-west-2"
            ]
        }
    }
}

Checklist

• Are there new checks included in this PR? 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.

License

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.86%. Comparing base (9794b5c) to head (c9de0b9).
Report is 6 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5973      +/-   ##
==========================================
+ Coverage   92.78%   92.86%   +0.07%     
==========================================
  Files          58       58              
  Lines        4867     4919      +52     
==========================================
+ Hits         4516     4568      +52     
  Misses        351      351              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vicferpoy]

This looks really good, great job! I left a few suggestions and one required change. Feel free to discuss anything since I lack some context about the requirements here.

[vicferpoy]

@AdriiiPRodri Also, I forgot to mention this filter could be vastly improved using the logic from the inserted_at filter from the base Findings filterset:

    def filter_inserted_at(self, queryset, name, value):
        value = self.maybe_date_to_datetime(value)
        start = uuid7_start(datetime_to_uuid7(value))

        return queryset.filter(id__gte=start).filter(inserted_at__date=value)

Please take a look at how it is done in the base findings filters, because it takes partitioned tables into consideration and improves efficiency by a lot.

[AdriiiPRodri]

@AdriiiPRodri Also, I forgot to mention this filter could be vastly improved using the logic from the inserted_at filter from the base Findings filterset:

    def filter_inserted_at(self, queryset, name, value):
        value = self.maybe_date_to_datetime(value)
        start = uuid7_start(datetime_to_uuid7(value))

        return queryset.filter(id__gte=start).filter(inserted_at__date=value)

Please take a look at how it is done in the base findings filters, because it takes partitioned tables into consideration and improves efficiency by a lot.

Fixed in the last commit, thanks!