Allow View subclasses to define async method handlers.

[Carlton Gibson]

The current ​topic docs for Async views say this about class-based views:

For a class-based view, this means making its __call__() method an async def (not its __init__() or as_view()).

This isn't really appropriate for Django's class-based views:

• We don't implement __call__(), rather going via as_view() — for a per-request instance — and then dispatch().
• Users expect to implement the HTTP method handlers — get(), post(), and so on — rather than these more internal bits.

Ideally we'd allow specifying async def at the method handler level, to allow using await in the handler, and writing views such as this:

    import asyncio
    from django.http import HttpResponse
    from django.views import View

    class AsyncView(View):
        async def get(self, request, *args, **kwargs):
            # Perform io-blocking view-logic using await, sleep for example.
            await asyncio.sleep(1)
            return HttpResponse("Hello async world!")

[Carlton Gibson]

​PR

[GitHub <noreply@…>]

In 9ffd4ea:

Fixed #33611 -- Allowed View subclasses to define async method handlers.