add the option to exclude fields

[uribracha2611]

Is your feature request related to a problem? Please describe.
Currently, the /v2/creatures endpoint requires explicit inclusion via the ?fields parameter. When a resource has a large number of fields and I only need to omit one or two, the request becomes incredibly verbose and difficult to maintain. If the API schema updates with new fields, I have to manually update my query strings just to receive that new data.

Describe the solution you'd like
I would like to see an ?exclude (or ?omit) parameter implemented. This would allow users to specify a comma-separated list of fields they do not want returned, while automatically including everything else.

Describe alternatives you've considered
I am currently using the ?fields parameter to whitelist every required field. However, this is inefficient for my use case because the vast majority of the fields are necessary, and I am only trying to reduce payload size by removing a few specific, heavy, or unnecessary keys.

Additional context
none

[calumbell]

Thanks for submitting this. Agree that excludes would likely be the best name for this query parameter.

A little precursory research suggests that the best way to handle this might be to write a mixin to read the exclude and apply the filtering, then having our model views inherit for it. The EagerLoadingMixin (/api_v2/views/mixins.py) might be a helpful model for code that interacts with query parameters