Feat/filter in request

[AMontagu]

• First step of Accept filters from request arguments and not only metadata #247

Before merging need:

• Add settings to control behavior with default to old behavior
• Add also pagination possibility to keep logic behavior
• Add documentation on filtering
• Add documention on new settings
• Add documentation disclaimer that default behavior will change in 1.0.0 to be accepting only filters from request by default
• update filter and pagination documentation with last plugin system
• Add documentation on Plugin
• Add documentation on MessageNameConstructor
• NOT A GOOD IDEA AFTERTHOUGHT - NOT DONE Create a plugin that inherit from requestlist, filter and pagination plugins to use in in List and Stream mixins
• Replace all depecrated arguments in fakeApp by plugin

[legau]

For the added fields in grpc actions I would suggest going the other way around and delegating this to the genericservices themselves to have more flexibility

something like :

class Service:
    def _extra_action_fields(self) -> list[ProtoField]: 
        return []

class GenericService(Service):
    filterset_class = MyFilterSet
    pagination_class = MyPagination

    @classmethod
    def _additional_action_fields(self):
        ...
        filter_field = ProtoField(...)
        pagination_field = ProtoField(...)
        ...
        return [*super()._extra_action_fields(), filter_field, pagination_field]
    
class GrpcAction:
    def make_proto_rpc(..., service):
        self.create_proto_message(..., additional_fields=service._additional_action_fields())
    
class ProtoMessage:
    def create(..., additional_fields: list[ProtoField]):
        ...