Pydantic model in responses is overwritten by request serializer

[araggohnxd]

Describe the bug
When declaring a DRF view decorated with @extend_schema, if the responses argument is a Pydantic model and the request argument is a DRF serializer, the response payload will be overwritten by that of the request serializer, both in Swagger and Redoc UI.

While testing to reproduce, I figured that it has something to do with the naming of the model and serializer. In the example below, if MyModel is renamed to something like MyPydanticModel, or something else that doesn't overlap with the initial portion of the serializer name MyModelSerializer, it seems to work properly.

To Reproduce

from rest_framework import serializers, views
from rest_framework.response import Response
from rest_framework.request import Request
from pydantic import BaseModel
from drf_spectacular.utils import extend_schema


class MyModelSerializer(serializers.Serializer):
    field1 = serializers.CharField()
    field2 = serializers.IntegerField()


class MyModel(BaseModel):
    other_field1: str
    other_field2: int


@extend_schema(
    request=MyModelSerializer,
    responses=MyModel,
)
class MyView(views.APIView):
    def post(self, request: Request):
        serializer = MyModelSerializer(data=request.data)
        serializer.is_valid(raise_exception=True)

        response = MyModel(
            other_field1=serializer.validated_data['field1'],
            other_field2=serializer.validated_data['field2'],
        )

        return Response(response.model_dump())

Expected behavior