Option to generate OpenAPI schema from docstring if verbose_name not defined

[Adrian-at-CrimsonAzure]

I would love if DRF had the ability to pull docstrings for field labels on API OPTIONS. Say I have the following example model:

class User(AbstractUser):
    """
    An Application user
    """
    
    company: Company = models.ForeignKey(Company, on_delete=models.PROTECT, null=True, blank=True)
    """Company this user belongs to"""
    username = None
    """Username is unused, see email field"""
    email: str = models.EmailField(_('email address'), unique=True)
    """User email address"""
    middle_name: str = models.CharField(null=True, blank=True, max_length=255)
    """User middle name"""
    phone_number: str = models.CharField(null=True, blank=True, max_length=50)
    """User phone number"""

    # etc...

That would make the corresponding OPTIONS for the /api/users endpoint:

{
    "name": "User",
    "description": "User info",
    "renders": [
        "application/json",
        "text/html"
    ],
    "parses": [
        "application/json",
        "application/x-www-form-urlencoded",
        "multipart/form-data"
    ],
    "actions": {
        "PUT": {
            "company": {
                "type": "field",
                "required": false,
                "read_only": false,
                "label": "Company this user belongs to"
            },
            "email": {
                "type": "email",
                "required": true,
                "read_only": false,
                "label": "Email address",
                "max_length": 254
            },
            "middle_name": {
                "type": "string",
                "required": false,
                "read_only": false,
                "label": "User middle name",
                "max_length": 255
            },
            "phone_number": {
                "type": "string",
                "required": false,
                "read_only": false,
                "label": "User phone number",
                "max_length": 50
            }
        }
    }
}

Our model documentation is pretty comprehensive, it would be a shame to have to duplicate all of that into the verbose_name field or something.