Incorrect number of arguments expected when dataclass is applied using __init_subclass__

Bug Report

A bit obscure and perhaps not a supported pattern, but using __init_subclass__ to turn subclasses into dataclasses in order to remove the need for library users to use the @dataclass decorator makes mypy confused about how many args the subclass' constructor expects.

To Reproduce

https://mypy-play.net/?mypy=latest&python=3.10&gist=d5900693474f425fc04dc5d36bd0eb2d

from dataclasses import dataclass


class Event:
    def __init_subclass__(cls):
        dataclass(cls)


class BaseEvent(Event):
    base_field: str


class SubEvent(BaseEvent):
    sub_field: str
    
    
SubEvent("base", "sub")

Expected Behavior

No errors from mypy.

Actual Behavior

In [1]: from dataclasses import dataclass
    ..: 
    ..: 
    ..: class Event:
    ..:     def __init_subclass__(cls):
    ..:         dataclass(cls)
    ..: 
    ..: 
    ..: class BaseEvent(Event):
    ..:     base_field: str
    ..: 
    ..: 
    ..: class SubEvent(BaseEvent):
    ..:     sub_field: str
    ..: 
    ..: 
    ..: SubEvent("base", "sub")
    ..: 
Out[1]: SubEvent(base_field='base', sub_field='sub')

main.py:17: error: Too many arguments for "SubEvent"
Found 1 error in 1 file (checked 1 source file)

Your Environment

• Mypy version used: 0.910
• Mypy command-line flags: None
• Mypy configuration options from mypy.ini (and other config files): None
• Python version used: 3.10
• Operating system and version: n/a (playground)

Start with the linked mypy-play reproducer and compare how mypy handles dataclasses applied in init_subclass with ordinary @dataclass usage. Trace the constructor-argument inference for BaseEvent and SubEvent, then verify that mypy accepts SubEvent("base", "sub") without errors.