Add Dynamic Api View to framework

[Merser4]

Hello everyone. Currently in DRF there are 2 types of class-based views ApiView and ViewSet. ApiView cannot implement multiple methods that will handle multiple paths. This problem is partially solved by ViewSet, but it also has problems. Inconvenient comparison with http methods, a lot of implicit magic. Also, if some ViewSet methods require some specific classes parsers/renderers/permissions... then this turns into an unreadable combiner. I have an idea and sketched code to implement a new View. What it will roughly look like.

class User(DynamicApiView):
    authentication_classes = [TokenAuthentication]
    permission_classes = [IsAuthenticated]
    throttle_classes = []

    @get(path='/', trottles=[UserRateThrottle], name='users-list')
    def get_users(self, requests)
        ...

    @get(path='<int:pk>/')
    def retrieve_user(self, request, pk)
        ...

    @post(path='/', authentications=None, permissions=None)
    def create_user(self, request)
        ...

    @patch(path='<int:pk>/change_password/', permissions=[IsOwner])
    def change_user_password(self, request, pk)
        ...

    @delete(path='<int:pk>/', permissions=[IsOwner])
    def delete_user(self, request, pk)
        ...

In ../urls.py

urlpatterns = [
    *router(base_path='api/v1/users/, User),
]

And we get
urlpatterns = [
    URLPattern(path='api/v1/users/', ...),
    URLPattern(path='api/v1/users/<int:pk>/', ...),
    URLPattern(path='api/v1/users/<int:pk>/change_password', ...),
]

With this implementation, it is more convenient to write a View with a large number of methods and everything looks more explicit. Decorators are for convenience and in Runtime they will be removed and all dependencies will go into the class. They can also be extended with various dependencies as in FastApi.