Closes #7598: Enable custom field filtering for GraphQL

[jeremystretch]

Closes: #7598

This PR serves to capture @jeremypng's recent work on improving the GraphQL API. Although this work primarily targets FR #7598, it includes many foundational improvements:

• Discontinuing the use of deprecated filters (USE_DEPRECATED_FILTERS = False)
• Defining standalone filters for GraphQL
• Reusable mixin classes for filters
• Adds the as_enum() method to ChoiceSet for use in GraphQL filters

[jeremystretch]

We still need to update the documentation to cover:

• The new filtering syntax for GraphQL queries
• Developer instructions for adding & updating GraphQL filters

[jeremystretch]

I believe this PR also resolves the following bugs related to GraphQL functionality:

• GraphQL filter for "ip_address_list" - Filter query tag works not as accepted #16305
• Missing lookup filters for interface object fields #16511
• Cannot filter ip range based on parent prefix #17681
• GraphQL filters (AND, OR and NOT) don't work for custom filterset fields #17688

[jeremypng]

We have continued using this graphql filtering system on 4.0.11 and have reduced nested queries that were taking 36s with pynetbox and the DRF API to 400ms with graphql.

The additional changes you have made look good.

[jeremystretch]

@jeremypng do you know whether it's necessary to define these filters explicitly? Setting them to auto seems to yield the same schema, but I wanted to check if you had run into any problems with this approach.

Suggested change

	xconnect_id: FilterLookup[str] | None = strawberry_django.filter_field()
	xconnect_id: strawberry.auto

[jeremypng]

If it can successfully infer the filter type from the field type it will work. From what I saw, this generally works for model fields that are physical database fields but not computed fields.

[jeremystretch]

That makes sense, thanks!

[arthanson]

Adding a couple sample queries here for anyone testing to play with:

{
  site_list(
    filters: {status: STATUS_PLANNED, OR: {tenant: {name: {exact: "Foo"}}}}
  ) {
    name
  }
}

{
  ip_address_list(
    filters: {parent:["172.16.0.1"]}
  ) {
    address
    status
  }
}

[arthanson]

Couple small suggestions, but it could go in even without those.