Fixes #20422: Allow Aggregate and Prefix to filter by family in GraphQL

[rinna11]

Fixes: #20422

This allows AggregateFilter and PrefixFilter to filter by their family similar with IPAddressFilter.
I've tested the following queries manually:

aggregate_v6: aggregate_list(filters: {family: FAMILY_6}) {
    prefix
}
prefixes_v4: prefix_list(filters: {family: FAMILY_4}) {
    prefix
    role {
      name
    }
    vrf {
      name
    }
    vlan {
      vid
    }
}

[jnovinger]

Thanks for the work, @rinna11. The approach looks good and correctly follows the existing pattern.

Please add tests covering the family filter for both AggregateFilter and PrefixFilter, with both FAMILY_4 and FAMILY_6 values to verify the filter returns the correct address family results.

You can add custom test methods to the AggregateTest and PrefixTest classes in ipam/tests/test_api.py. These inherit from APIViewTestCase which provides self.client, self.user, and other helpers. Please mark these tests with @tag('regression'), which you can see elsewhere in the same file. For examples, see the templated tests that are defined in netbox/tests/test_graphql.py.

[rinna11]

Hi @jnovinger , thank you for the suggestion!
I had a quick look at ipam/tests/test_api.py, and it seems there aren’t any existing GraphQL filter tests for AggregateTest and PrefixTest there. I did find relevant filtering tests in ipam/tests/test_filtersets.py, and those already include conditions for filtering by family. These tests are passing both in the current codebase and with this PR.
Also, when the family field was enabled for IPAddressFilter in #19621 , adding specific filter tests wasn’t required at that time either.

Given that, I would like to kindly ask if we could proceed with merging this PR without adding new tests. Please let me know if you're still up for it after all that—happy to adjust!
Thanks again for your time and review.