[Python APIView] Type annotation rendered as 'any' instead of 'Any' for HttpRequest.content

Bad code snippet:

content: any

What it should do:
- The language parser is rendering the typing annotation as the built-in name "any" instead of the typing type. "any" is a built-in function, not a typing type, so the stub is misleading and can cause errors or incorrect type information. The parser should render the annotation as typing.Any (or Any with an appropriate import).

Good code snippets:

Option A (preferred, explicit import):
from typing import Any

content: Any

Option B (qualified):
import typing

content: typing.Any

Please fix the parser so that type annotations referring to the generic Any are rendered as typing.Any or Any with the corresponding import, rather than the built-in name "any".

Start with the APIView language parser and reproduce the issue using the HttpRequest.content annotation shown in the report. Trace how the generic Any annotation is rendered; done means the generated stub uses typing.Any or Any with an appropriate import instead of the built-in any.

Written by the indexing model from the issue text.